Data Analyzer Administrator Guide

Informatica® PowerCenter®
(Version 8.6)

Informatica PowerCenter Data Analyzer Administrator Guide Version 8.6 June 2008 Copyright © 2001-2008 Informatica Corporation. All rights reserved. Printed in the USA. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are 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. This Software may be protected by U.S. and/or international Patents and other Patents Pending. 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 and 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 product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica Complex Data Exchange and Informatica On Demand Data Replicator 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 and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright © Sun Microsystems. All rights reserved. Copyright © Aandacht c.v. All rights reserved. Copyright 2007 Isomorphic Software. All rights reserved. This product includes software developed by the Apache Software Foundation (http://www.apache.org/) and other software which is licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright, Red Hat Middleware, LLC, all rights reserved; software copyright © 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, “as-is”, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. This product includes software copyright (C) 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://www.gnu.org/software/ kawa/Software-License.html. This product includes software licensed under the terms at http://www.bosrup.com/web/overlib/?License. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/. This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php). This Software is protected by Patents including US Patents Numbers 6,640,226; 6,789,096; 6,820,077; and 6,823,373 and other Patents Pending. 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 noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

Part Number: DA-ADG-86000-0001

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Chapter 1: Data Analyzer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Data Analyzer Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Main Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Supporting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Data Analyzer Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Using Data Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Configuring Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Data Lineage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Data Lineage for a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Data Lineage for a Metric or Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Data Analyzer Display Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Language Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Setting the Default Expression for Metrics and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 8 Date and Number Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Exporting Reports with Japanese Fonts to PDF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2: Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Restricting User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Setting Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Authentication Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 User Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Managing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Editing a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Editing a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Adding Data Restrictions to a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3: Setting Permissions and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Setting Access Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
iii

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Viewing Attached Reports. . . . . . . . . . . . . . 34 Stopping an Event-Based Schedule Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Editing a Time-Based Schedule . . . . . . . . . . . . . . . 33 Editing Access Permissions for an Event-Based Schedule . . . . . . . . . . . . . . . . . . . . 36 Viewing Task Properties . . . . . . . Create an Event-Based Schedule . . . 26 Viewing Attached Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Step 1. . . . . . . 27 Viewing or Clearing a Task History . . . . . . . . . . . . . . 35 Disabling an Event-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Understanding Data Restrictions for Multiple Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Chapter 4: Managing Time-Based Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Removing an Event-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Updating Reports When a PowerCenter Session Completes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Managing Time-Based Schedules . Use the PowerCenter Integration Utility in PowerCenter . . . . . . . . . . . . . . . . 17 Restricting Data Access by User or Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Editing Access Permissions for a Time-Based Schedule . . . 17 Restricting Data Access by Object . . . . . . . . . . . . . 36 iv Table of Contents . . . 25 Attaching Reports to a Time-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Managing Event-Based Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Viewing or Clearing an Event-Based Schedule History . . . . . . . . . . . . . 25 Managing Reports in a Time-Based Schedule . . . . . . . . . . . 27 Using the Calendar . 28 Navigating the Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Monitoring a Schedule . . . . . . . . . . . . . . . . . . . . . . . 24 Stopping a Time-Based Schedule Immediately . . . . . . . . . . . . . . . . . . . . 21 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Overview . . 27 Removing a Report from a Time-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Starting an Event-Based Schedule Immediately . . . . . . . . . . . . . . . . . . .Restricting Data Access . . . . . . 24 Starting a Time-Based Schedule Immediately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Stopping a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Viewing Task Properties . 25 Removing a Time-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Viewing or Clearing a Time-Based Schedule History . . . . . . . . . 32 Step 2. . . . . . . . . . . . . . . . . 35 Managing Reports in an Event-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Creating a Time-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Chapter 5: Managing Event-Based Schedules . . . . . . . . . . 28 Defining a Business Day . . . . . . . . . . . . . 25 Disabling a Time-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Defining a Holiday . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Using Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Editing an Event-Based Schedule . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . 36 Removing a Report from an Event-Based Schedule . . . . . . . . 65 Overview . . . . . . . . . . . . . . 60 Importing a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Importing a Security Profile . . . . . . . . 69 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Importing Objects from a Previous Version . . . . . . . . . . . . . . . 50 Object Permissions . . . . . . . . . 37 Attaching Imported Cached Reports to an Event-Based Schedule . . . . . . . . . . . . . . . . . . . . . . . . 40 Exporting Metric Definitions Only . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Troubleshooting . . . . . . . . . . . . . . . . . . . . 47 Chapter 7: Importing Objects to the Repository . . . . . . . . . . . . . . . . . . . . . . . 50 Importing a Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Viewing or Clearing a Report History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Running the Import Export Utility . . . 42 Exporting a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Importing a Large Number of Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Exporting a Schema . . . . . . . . . 55 Importing a Global Variable . . . . . . . . . . . . . . . . . . . . 40 Exporting Metrics and Associated Schema Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Importing a Group Security Profile . . . . 59 Importing a User Security Profile . . . . . . . . . . . . . . . 66 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Exporting a Group Security Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Exporting a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Exporting a Security Profile . . . . . . . . . . . . . . . . . . . 44 Exporting a Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Exporting a User Security Profile . . . . . . . . . . . . . . . . 53 Importing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Importing Reports from Public or Personal Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Exporting a Time Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Importing a Time Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Importing a Dashboard . . . . . . . . . . . . . . 49 Overview . . . . . . . . . . . . . . . . . . . . . . . . 37 Chapter 6: Exporting Objects from the Repository . . . . . . . . . . . . . 49 XML Validation . . . . . 71 v . . . . . . . . . . . 46 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Using SSL with the Import Export Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Steps for Importing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Chapter 8: Using the Import Export Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Overview . . . . . . . . . . . . . . . . . . . . . . . . 42 Exporting a Global Variable . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . 75 Creating a Color Scheme . . . . . . . . . . . . . . . . . . . . . . . . . 93 Data Analyzer Administrative Reports Folder . . . . . . . . . . . . . . . . 74 Using a Predefined Color Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Chapter 10: Working with Data Analyzer Administrative Reports . . . . . . . . . . . . . 83 Specifying Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 9: Managing System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Configuring Report Table Scroll Bars. 81 Managing LDAP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring the System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Step 1. . . . . . . 85 Setting Query Rules at the System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Database . . . . . . . . . . . . . . . . . 81 Managing Delivery Settings. . . . . . . . . . . . . . . . 93 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Setting Up the Data Analyzer Administrative Reports . . . . . . . . . . . . . . . . 88 Configuring Departments and Categories . . . . . . . 99 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Managing Color Schemes and Logos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Setting Query Rules at the Report Level . . . . . . . . . . . . . . . . . . . . 95 Step 4. . . . . . . . 78 Managing Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Configuring Report Headers and Footers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Assigning a Color Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 vi Table of Contents . . . . . . . . . . . . 85 Setting Query Rules at the User Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Step 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Setting Query Rules at the Group Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Configuring Display Settings for Groups and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Overview . . . . . . . . . . . . . . . . 97 Chapter 11: Performance Tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Step 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Import the Data Analyzer Administrative Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add the Data Source to a Data Connector . . . . . . . . . . 96 Using the Data Analyzer Administrative Reports . . . . . . . . . . . . . . . . . . . . . . . . . 76 Selecting a Default Color Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Configuring the External URL . . . . . . . . . . . 78 Viewing the User Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Editing a Predefined Color Scheme . . . . . . . . . . . . . . . . . . . . . . 83 Configuring the Mail Server . . . . . . . . . . . . . . . . . . . . . . Set Up a Data Source for the Data Analyzer Repository . . . . . . . . . . . . . . . . . . . Add the Administrative Reports to Schedules . . . . . . . . . . . . . . 83 Configuring SMS/Text Messaging and Mobile Carriers . . . . . . . . . . . 84 Viewing System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Configuring and Viewing the Activity Log . . . . . 84 Setting Rules for Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Administrator’s Dashboard . . . . . . . . . . . . . . . . . . . . . 80 Configuring the JDBC Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . 119 Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Number of Charts in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Ranked Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Chart Legends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 JSP Optimization . . . . . . . . . . . . . . . . . . . . . 117 Using the Data Analyzer API Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 HP-UX . . . . . . . . . . . . . . . . . . 111 Datatype of Table Columns . . . . . . . . . . . . . . . . . 121 HTML Hexadecimal Color Codes . . . . . 113 Frequency of Schedule Runs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Repository Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Data Analyzer Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Date Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Connection Pool Size for the Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Indicators in Dashboard . . . . . . . . . . . 114 Purging of Activity Log . . . . . . . . . . 107 EJB Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Recommendations for Dashboard Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Row Limit for SQL Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Setting the UI Configuration Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 UI Configuration Parameter in Data Analyzer URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 AIX . . . . . 101 Microsoft SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Overview . . . . . . . . . . . . . . . . . . . . . . 118 Default UI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 JavaScript on the Analyze Tab . . . . . . . . . . . . 112 Interactive Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Appendix A: Hexadecimal Color Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Scheduler and User-Based Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Table of Contents vii . . . 118 Setting Up Color Schemes and Logos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Application Server . . . . . . . . . . . . . . . . . . . . . . 101 Operating System . . . . . . . . . 117 Using the Data Analyzer URL API . . . . . . . . . . . . . . . . . . . . . . . 115 Server Location . . . . . . . . . . . . . . . . . . . . . . . . . 101 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Servlet/JSP Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Chapter 12: Customizing the Data Analyzer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Appendix B: Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Configuring the Eviction Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .properties . . 143 viii Table of Contents . . . . . . . . . . 137 Configuring the Lock Acquisition Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xml . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Properties in DataAnalyzer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Properties in web. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Index . . . . . . . . .xml . 129 Modifying the Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Overview . . . . . . . . . . . . . 130 Properties in infa-cache-service. . . . . . . . . .

including managing user access and report schedules and exporting and importing objects in a Data Analyzer repository. you can access the Informatica Customer Portal site at http://my. its background. The services area of the site includes important information about technical support. technical white papers. and access to the Informatica user community.informatica. You can also find answers to frequently asked questions. and implementation services.com. user group information. The site contains product information. Informatica Knowledge Base As an Informatica customer. It assumes that you have knowledge of relational databases. you can access the Informatica Knowledge Base at http://my. The Data Analyzer Administrator Guide is written for system administrators. Informatica Web Site You can access the Informatica corporate web site at http://www.informatica.com. Informatica Documentation Center. contact the Informatica Documentation team through email at infa_documentation@informatica. It also discusses performance tuning and server clusters. usable documentation. and web technology. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. Informatica Resources Informatica Customer Portal As an Informatica customer. newsletters. If you have questions. comments. You will also find product and partner information. and technical tips. and sales offices. upcoming events.Preface The Data Analyzer Administrator Guide provides information on administering Data Analyzer. We will use your feedback to improve our documentation.com.com. training and education. ix . Informatica Documentation The Informatica Documentation team takes every effort to create accurate. the Informatica Knowledge Base. SQL. or ideas about this documentation.informatica. The site contains information about Informatica. access to the Informatica customer support case management system (ATLAS). Let us know if we can contact you regarding your comments.

3rd Floor 150 Airport Road Bangalore 560 008 India Toll Free Australia: 1 800 151 830 Singapore: 001 800 4632 4357 Standard Rate India: +91 80 4112 5738 Toll Free +1 877 463 2435 Toll Free 00 800 4632 4357 Standard Rate Brazil: +55 11 3523 7761 Mexico: +52 55 1168 9763 United States: +1 650 385 5800 Standard Rate Belgium: +32 15 281 702 France: +33 1 41 38 92 26 Germany: +49 1805 702 702 Netherlands: +31 306 022 797 United Kingdom: +44 1628 511 445 x Preface . or the WebSupport Service.com. White Waltham Maidenhead. Diamond District Tower B.com for technical inquiries support_admin@informatica. Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Informatica Corporation Headquarters 100 Cardinal Way Redwood City. Ltd. California 94063 United States Europe / Middle East / Africa Informatica Software Ltd.informatica. 6 Waltham Park Waltham Road. You can request a user name and password at http://my. email. You can contact a Customer Support Center through telephone.com for general customer service requests WebSupport requires a user name and password.Informatica Global Customer Support There are many ways to access Informatica Global Customer Support. Use the following email addresses to contact Informatica Global Customer Support: ♦ ♦ support@informatica. Berkshire SL6 3TN United Kingdom Asia / Australia Informatica Business Solutions Pvt.

5 Data Lineage. format. or create and run custom reports. 1 Data Analyzer Framework. You can use Data Analyzer to run PowerCenter Repository Reports. To display real-time data in a Data Analyzer real-time report. 7 Introduction PowerCenter Data Analyzer provides a framework for performing business analytics on corporate data. 5 Localization. With Data Analyzer. Metadata Manager Reports. and analyze corporate information from data stored in a data warehouse. A hierarchical schema contains attributes and metrics from an XML document on a web server or an XML document returned by a web service operation. Based on a dimensional data warehouse in a relational database. The Reporting Service is the application service that runs the Data Analyzer application in a PowerCenter domain. Hierarchical schema. you create a Data Analyzer real-time message stream 1 . Each schema must contain all the metrics and attributes that you want to analyze together. Data Analyzer uses the characteristics of a dimensional data warehouse model to assist you to analyze data. you define the tables in the schema. or other data storage models. see the PowerCenter Administrator Guide. ♦ ♦ Data Analyzer supports the Java Message Service (JMS) protocol to access real-time messages as data sources. operational data store.CHAPTER 1 Data Analyzer Overview This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ Introduction. 4 Security. Data Analyzer uses the familiar web browser interface to make it easy for a user to view and analyze business information at any level. For more information about the Reporting Service. Data Analyzer works with the following data models: ♦ Analytic schema. Use the operational schema to analyze data in relational database tables that do not conform to the dimensional data model. Identify which tables contain the metrics and attributes for the schema. Based on an operational data store in a relational database. you define the fact and dimension tables and the metrics and attributes in the star schema. Data Profiling Reports. Based on data in an XML document. When you set up an analytic schema in Data Analyzer. You can create a Reporting Service in the PowerCenter Administration Console. and define the relationship among the tables. you can extract. 2 Data Analyzer Basics. Operational schema. When you set up an operational schema in Data Analyzer. filter.

and other objects in the Data Analyzer repository. Application Server JBoss Application Server helps the Data Analyzer Application Server manage its processes efficiently. The Java application server provides services such as database access and server load balancing to Data Analyzer. and how to present the report. You need a separate web server to set up a proxy server to enable external users to access Data Analyzer through a firewall. The data for an analytic or operational schema must also reside in a relational database. When you create a Reporting Service. you can read data from a data source. It includes components and services that may already exist in an enterprise infrastructure. The data for a hierarchical schema resides in a web service or XML document. Data Analyzer stores metadata for schemas. Data Analyzer uses the following Java technology: ♦ ♦ ♦ Java Servlet API JavaServer Pages (JSP) Enterprise Java Beans (EJB) 2 Chapter 1: Data Analyzer Overview . and view the results on the web browser. Data Analyzer uses the application server to handle requests from the web browser. It generates the requested contents and uses the application server to transmit the content back to the web browser. When you run reports for any data source. network. In Data Analyzer. Main Components Data Analyzer is built on JBoss Application Server and uses related technology and application programming interfaces (API) to accomplish its tasks. Data Analyzer Data Analyzer is a Java application that provides a web-based platform for the development and delivery of business analytics. Data Analyzer stores metadata in a repository database to keep track of the processes and objects it needs to handle web browser requests. The Reporting Service configures the Data Analyzer repository with the metadata corresponding to the selected data source. If the application server contains a web server. metrics and attributes. user profiles. The Data Analyzer repository must reside in a relational database. you need to specify the Data Analyzer repository details. Note: If you create a Reporting Service for another reporting source. Data Analyzer uses the metadata in the Data Analyzer repository to determine the location from which to retrieve the data for the report. and system resources.with the details of the metrics and attributes to include in the report. you do not need to install a separate web server. create reports. reports. Web Server Data Analyzer uses an HTTP server to fetch and transmit Data Analyzer pages to web browsers. Data Analyzer updates the report when it reads JMS messages. you need to import the metadata for the data source manually. such as an enterprise data warehouse and authentication server. JBoss Application Server is a Java 2 Enterprise Edition (J2EE)compliant application server. queries. Data Analyzer Framework Data Analyzer works within a web-based framework that requires the interaction of several components. The Java Application Server also provides an environment that uses Java technology to manage application.

see the PowerCenter Administrator Guide. You launch Data Analyzer from the Administration Console. PowerCenter You create and enable a Reporting Service on the Domain page of the PowerCenter Administration Console. the Administration Console starts Data Analyzer. and other objects and processes. Supporting Components Data Analyzer has other components to support its processes. or it can be generated by a web service operation. It connects to the database through JDBC drivers. Forward reports through email. Data Analyzer reads data from an XML document. personalization. You can only modify the user settings such as the user name or the contact details in Data Analyzer. For hierarchical schemas. When you use the Administration Console to create native users and groups. The Reporting Service copies the users and groups to the Data Analyzer repository. or change user passwords in Data Analyzer. the Service Manager stores the users and groups in the domain configuration database and notifies the Reporting Service. PowerCenter Client tools. or Metadata Manager Reports. For more information about authentication methods. Data Analyzer Framework 3 . You log in to Data Analyzer to create and run reports on data in a relational database or to run PowerCenter Repository Reports. Although you can use Data Analyzer without these components. or by accessing the Data Analyzer URL from a browser. including an API that allows you to integrate Data Analyzer features into other web applications and security adapters that allow you to use an LDAP server for authentication. Data Analyzer connects to the XML document or web service through an HTTP connection. You can create reports based on the schemas without accessing the data warehouse directly. user profiles. Data Analyzer connects to the repository with JDBC drivers. Data Analyzer reads data from a relational database. or Metadata Manager. you can extend the power of Data Analyzer when you set it up to work with these additional components. The metadata includes information on schemas. Data Analyzer Data Profiling Reports. reports and report delivery. Authentication Server You use PowerCenter authentication methods to authenticate users logging in to Data Analyzer. Data Source For analytic and operational schemas. The XML document can reside on a web server. Note: You cannot create or delete users and groups. Mail Server Data Analyzer uses Simple Mail Transfer Protocol (SMTP) to provide access to the enterprise mail server and facilitate the following services: ♦ ♦ Send report alert notification and SMS/Text Messages to alert devices.♦ ♦ ♦ Java Database Connectivity (JDBC) Java Message Service (JMS) Java Naming and Directory Interface (JNDI) Data Analyzer Repository The repository stores the metadata necessary for Data Analyzer to track the objects and processes that it requires to effectively handle user requests. When you enable the Reporting Service.

Create a dashboard and customize it to display the indicators and links to reports and shared documents to which you want immediate access. Set up the connectivity information so that Data Analyzer can access the data warehouse. web service. 4. set up the tables for an operational schema. You need system administrator privileges to define data sources. Set up the data connector. Data Analyzer has many more features you can use to analyze and get the most useful information from your corporate data. and other objects and display them in any web application or portal. You need system administrator privileges to import table definitions or define rowsets. Define the data source. Create indicators and alerts for the report. Set up alerts on reports based on events and threshold values that you define. Data Analyzer Basics This section lists the steps you need to complete to access analytic data in Data Analyzer.xml file. if you log in to Data Analyzer. Define the fact and dimension tables for an analytic schema. If you set up an analytic schema. Define the metrics and attributes in the schemas. You can set the session timeout period according to the Data Analyzer usage in your organization. The API specifies the functions available to developers to access Data Analyzer dashboards. Define the rowsets and columns for web services or XML data sources. You need system administrator privileges to define the schemas in Data Analyzer. Define an analytic. To preserve application resources. Create dashboards. set up a time dimension. 6. This book presents the tasks that a system administrator typically performs in Data Analyzer. You need system administrator privileges to set up data connectors. 4 Chapter 1: Data Analyzer Overview . For more information. You can configure Data Analyzer to access more than one data source. but you do not use it for 30 minutes. 3. Import the table definitions from JDBC data sources or set up rowsets and columns from XML sources. or hierarchical schema. Create reports based on the metrics and attributes you define. Set up schedules to run reports regularly. operational. or define a hierarchical schema. Create analytic workflows to analyze the data. Create and run reports. or XML documents. the session terminates or times out. 5. Create a data connector to identify which data source to use when you run reports. Import table definitions from the data warehouse or operational data store into the Data Analyzer repository. reports. 7. Data Analyzer terminates a user session if it does not have any activity for a length of time. 2. Configuring Session Timeout By default. Using Data Analyzer When you use Data Analyzer to analyze business information. The system administrator can change the session timeout period by editing the value of the session-timeout property in the web.Web Portal The Data Analyzer API enables you to integrate Data Analyzer into other web applications and portals. complete the following steps: 1. see “Configuration Files” on page 129.

Security and data integrity in the database servers that contain the data warehouse and the repository are essential for a reliable system environment. Data Analyzer depends on database servers to provide their own security and data integrity facilities. or attribute displays one or more of the following objects: ♦ ♦ Data Analyzer repositories. see the PowerCenter Administrator Guide. and metrics. You can access data lineage for metrics. Data Lineage You can access the data lineage for Data Analyzer reports. When you access data lineage from Data Analyzer. Data Analyzer connects to a Metadata Manager server. In the data lineage.Security Data Analyzer provides a secure environment in which to perform business analytics. Data Analyzer reads data from the data warehouse and stores data in a repository to support its different components. and reports from the following areas in Data Analyzer: Data Analyzer Object Report Metric Access Data Lineage From. attributes. Data structures. Fields are objects within data structures that store the metadata.. You can load objects from multiple Data Analyzer repositories into Metadata Manager. For a Data Analyzer data lineage. how it transforms. Use data lineage to understand the origin of the data. attributes. Metadata Manager displays metadata objects for each repository.. You manage users and groups in the PowerCenter Administration Console. the data structures include the following: − − − − Reports Fact tables Dimension tables Table definitions ♦ Fields. Data structures group metadata into categories. The Metadata Manager server displays the data lineage in an Internet Explorer browser window. It supports standard security protocols like Secure Sockets Layer (SSL). For more information about the PowerCenter authentication methods. For a Data Analyzer data lineage. Data Analyzer uses the PowerCenter authentication methods to authenticate users set up in the PowerCenter domain configuration database. fields include the following: − Metrics in reports Security 5 . It also provides system administrators a way to control access to Data Analyzer tasks and data based on privileges and roles granted to users and groups. Find tab Schema Directory > Metrics page Create > Report > Select Metrics page Analyze tab Schema Directory > Attributes page Create > Report > Select Attributes page Analyze tab Attribute Data lineage for a Data Analyzer report. metric. and where it is used. Metadata Manager is the PowerCenter metadata management and analysis tool. Use the PowerCenter Administration Console to configure data lineage for a Reporting Service. You cannot use data lineage with the Mozilla Firefox browser.

Repository. the following data structures display in the data lineage: ♦ ♦ ♦ ♦ Data Analyzer report: Sales report Data Analyzer dimension tables: Countries. After you access the data lineage. Name of the field. or PDF file. You can export the data lineage to an HTML. For more information. the data lineage shows that the COUNTRIES table definition populates the Countries dimension table. Each field contains the following information: ♦ ♦ ♦ The direction of the arrows in the data lineage shows the direction of the data flow. Data Lineage for a Report Fields Data Structures Repository In Figure 1-1. You can display data lineage on the Internet Explorer browser. In Figure 1-1. Data Lineage for a Report You can access data lineage for cached and on-demand reports. Name of the Data Analyzer repository that contains metadata for the report. Data lineage shows the flow of the data displayed in a report. REGIONS. which provides the Country Name attribute for the Sales report. see the Metadata Manager User Guide. the parent for the Country Name field is the Countries dimension table. Field Name.− − Attributes in reports Columns in tables Note: The Metadata Manager server must be running when you access data lineage from Data Analyzer. fields are the metrics and attributes in the report. you can view details about each object in the data lineage. Data structure that populates the field. You can also email the data lineage to other users. In this example. In Figure 1-1. COSTS_DATA Parent. Excel. PA5X_RICH_SRC is the repository that contains metadata about the report. Figure 1-1 shows the data lineage for a Data Analyzer report: Figure 1-1. 6 Chapter 1: Data Analyzer Overview . You cannot display data lineage on the Mozilla Firefox browser. Regions Data Analyzer fact table: Costs Data Data Analyzer table definitions: COUNTRIES. For example.

UTF-8 character encoding is an ASCII-compatible multi-byte Unicode and Universal Character Set (UCS) encoding method. You must change the display language for the Data Analyzer login page separately in the browser. Data structures for reports that use the attribute. you must ensure that the language settings are correct when you complete the following tasks in Data Analyzer: ♦ Back up and restore Data Analyzer repositories. To avoid data errors. For more information about how to enable UTF-8 character encoding. Language Settings When you store data in multiple languages in a database. The data lineage also shows data structures for reports that use the metric or attribute. For more information. You change the display language for Data Analyzer in the Manage Accounts tab in Data Analyzer. Figure 1-2 show the data lineage for an attribute: Figure 1-2. enable UTF-8 character encoding in the Data Analyzer repository and data warehouse. Localization Data Analyzer uses UTF-8 character encoding for displaying in different languages.Data Lineage for a Metric or Attribute The data lineage for a metric or attribute is similar to the data lineage for a report. see the database documentation. Metadata Manager displays the data flow for that metric or attribute only. The repositories you back up and restore must have the same language type and locale setting or the repository you restore must be a superset of the repository you Localization 7 . see the Data Analyzer User Guide. Data Lineage for an Attribute The attribute name is the only field that appears in the data lineage. A language setting is a superset of another language setting when it contains all characters encoded in the other language. Data Analyzer Display Language You can change the display language for the Data Analyzer client regardless of the locale of the Data Analyzer server. The attribute name (Brand) appears within the data structure for the report. For a metric or attribute.

and time formats Data Analyzer displays.html 8 Chapter 1: Data Analyzer Overview . see the Data Analyzer Schema Designer Guide.back up. the repository you restore to must also support Japanese. Date and Number Formats The language setting for your Data Analyzer user account determines the numeric.adobe. Data Analyzer uses the format for the repository database language setting. You can find the Asian Font Package from the following web site: http://www. For example. ♦ Import and export repository objects. date. Data Analyzer uses the same expression regardless of the locale of the Data Analyzer server. Import table definitions from the data source. the repositories must have the same language type and locale setting or the destination repository must be a superset of the source repository. Exporting Reports with Japanese Fonts to PDF Files If a report contains Japanese fonts and you export the report to a PDF file. the language type and locale settings of the data warehouse and the Data Analyzer repository must be the same or the repository must be a superset of the data source. enter the date in the same format used in the data warehouse. When you import data warehouse table definitions into the Data Analyzer repository. If you want to use a different default expression for a different locale. ♦ Setting the Default Expression for Metrics and Attributes When you set the default expression for metrics and attributes. if the repository you back up contains Japanese data. you must change the default expression in the metric or attribute property. When you import an exported repository object. you must download the Asian Font Package from the Adobe Acrobat web site to view the PDF file. For more information. Save the Asian Font Package on the machine where you want to view the PDF file. When you enter a date in an SQL expression or define a date value for a global variable.com/products/acrobat/acrrasianfontpack. When Data Analyzer performs date calculations in calculated or custom metrics.

groups. groups. A user must have an active account to perform tasks and access data in Data Analyzer. Users in Data Analyzer need their own accounts to perform tasks and access data. 10 Managing Users. 9 Managing Groups. 9 . and roles. Users can perform different tasks based on their privileges. Restricting User Access You can limit user access to Data Analyzer to secure information in the repository and data sources. Authentication Methods The way you manage users and groups depends on the authentication method you are using: ♦ Native. Setting Permissions You can set permissions to determine the tasks that users can perform on a repository object. and roles for a Data Analyzer. You create and manage users. You can edit some user and group properties in Data Analyzer. groups. You assign privileges to users. groups. groups. Data Analyzer allows login access only to individuals with user accounts in Data Analyzer. and roles in the PowerCenter domain configuration database. Use the Security page of the PowerCenter Administration Console to create users. You set access permissions in Data Analyzer. see the PowerCenter Administrator Guide. To secure information in the repository and data sources.You can modify some user and group properties in Data Analyzer.CHAPTER 2 Managing Users and Groups This chapter includes the following topics: ♦ ♦ ♦ Overview. groups and roles in the Security page of the PowerCenter Administration Console. and roles in the domain configuration database. Users can perform different tasks based on their privileges. and roles in the PowerCenter Administration Console. 11 Overview You create users. For more information about creating users. PowerCenter stores the users.

their organization. and roles on the Security page of the Administration Console. and permission assignments with the list of users and groups in the Data Analyzer repository. the Service Manager stores the privilege.♦ LDAP authentication. see the PowerCenter Administrator Guide. You manage users and groups. or query governing settings. The Service Manager periodically synchronizes the list of users and groups in the repository with the users and groups in the domain configuration database. groups. You can restrict data access by group. Click Administration > Access Management > Groups. You manage the users and groups in the LDAP server but you create and manage the roles and privileges in the PowerCenter Administration Console. 3. or by accessing the Data Analyzer URL from a browser. The properties of the group appear. or assign a primary group to users in Data Analyzer. if you edit any property of a user in Data Analyzer. Editing a Group You can see groups with privileges on a Reporting Service when you launch the Data Analyzer instance created by that Reporting Service. the Service Manager synchronizes the users in the Data Analyzer repository with the updated LDAP users in the domain configuration database. To edit a group in Data Analyzer: 1. The Service Manager periodically synchronizes users in the LDAP server with the users in the domain configuration database. For more information. For more information about authentication methods. You cannot add users or roles to the group. When you assign privileges and roles to users and groups for the Reporting Service in the Administration Console or when you assign permissions to users and groups in Data Analyzer. you can edit some group properties such as department. the Service Manager does not synchronize the changes to the Data Analyzer repository. Metadata Manager. Similarly. In Data Analyzer. the Service Manager does not synchronize the domain configuration database with the modification. role. Managing Groups Groups allow you to organize users according to their roles in the organization. privileges. User Synchronization You manage users. In addition. The Service Manager stores users and groups in the domain configuration database and copies the list of users and groups to the Data Analyzer repository. For example. color schemes. you might organize users into groups based on their departments or management level. and which privileges and roles are assigned to them in the PowerCenter Administration Console. PowerCenter Client tools. Connect to Data Analyzer from the PowerCenter Administration Console. Note: If you edit any property of a user other than roles or privileges. 10 Chapter 2: Managing Users and Groups . 2. see the PowerCenter Administrator Guide. Select the group you want to edit and click Edit. The Groups page appears.

middle name. Query governing settings on the Groups page apply to reports that users in the group can run. it does not update the records in the domain configuration database. For more information. or last name of the user. Data Analyzer saves the modification in the Data Analyzer repository. PowerCenter Client tools. a user must have the appropriate privileges for the Reporting Service. For more information about these properties. see “Setting Rules for Queries” on page 85. Edit any of the following properties: Property Department Description Choose the department for the group. 3. Middle name of the user. For more information. You cannot assign a group to the user or define a primary group for a user in Data Analyzer. You assign privileges to a user. Click Administration > Access Management > Users. To edit a user account in Data Analyzer: 1. Select the user record you want to edit and click on it. For more information. Click OK to return to the Groups page. Last name of the user. 2. see “Managing Color Schemes and Logos” on page 74. see “Full Name for Data Analyzer Users” on page 12. If a user belongs to one or more groups in the same hierarchy level. see “Configuring Departments and Categories” on page 90. add the user to one or more groups. The Users page appears. or modify other properties of the account. and assign roles to the user in the PowerCenter Administration Console. Editing a User Account You can see users with privileges on a Reporting Service when you launch the Data Analyzer instance created by that Reporting Service. Data Analyzer displays the list of users that match the search string you specify. or by accessing the Data Analyzer URL from a browser. Connect to Data Analyzer from the PowerCenter Administration Console. You can edit a user account in Data Analyzer to change the color scheme. Color Scheme Assignment Query Governing 5.4. Managing Users 11 . Data Analyzer uses the largest query governing settings from each group. Enter a search string for the user in the Search field and click Find. When the Service Manager synchronizes with the Data Analyzer repository. The properties of the user appear. 5. Edit any of the following properties: Property First Name Middle Name Last Name Description First name of the user. If you edit the first name. 4. Assign a color scheme for the group. Managing Users Each user must have a user account to access Data Analyzer. Metadata Manager. To perform Data Analyzer tasks.

Department for the user. To add data restrictions to a user account. and last name based on the following rules: 1. Department Color Scheme Assignment Query Governing Note: Users can edit some of the properties of their own accounts in the Manage Account tab. For more information. <FirstName> [<MiddleName>] Any full name that contains a comma is converted to use the syntax without a comma: [<FirstName>] [<MiddleName>] <LastName> 3. For more information. You cannot edit this information. For more information. 12 Chapter 2: Managing Users and Groups . Data Analyzer uses this as the email for the sender when the user emails reports from Data Analyzer. click Administration > Access Management > Users. see “Configuring Departments and Categories” on page 90. middle. the full name is separated into first. Color schemes assigned at user level take precedence over color schemes assigned at group level. there is no middle name. middle. If the full name contains a comma. Full Name for Data Analyzer Users Data Analyzer displays the full name property in the PowerCenter domain as the following user account properties: ♦ ♦ ♦ First name Middle name Last name If the full name does not contain a comma. see “Restricting Data Access” on page 16. Data Analyzer sends the email to this address when it sends an alert notification to the user. the full name has the following syntax: [<FirstName>] [<MiddleName>] <LastName> Data Analyzer determines the full name as first. If no color scheme is selected. and then click the Data Restrictions button ( ) for the data for which you want to restrict user access. see “Setting Rules for Queries” on page 85. and last names based on the number of text strings separated by a space: ♦ ♦ If the full name has two text strings. 2. Unless users have administrator privileges. For more information. Specify query governing settings for the user. see “Managing Color Schemes and Logos” on page 74. Data Analyzer uses the default color scheme when the user logs in. the full name has the following syntax: <LastName>.Property Title Email Address Description Describes the function of the user within the organization or within Data Analyzer. The query governing settings on the User page apply to all reports that the user can run. You can associate the user with a department to organize users and simplify the process of searching for users. any string after the third string is included in the last name. After the conversion. If the full name has more than three text strings. Select the color scheme to use when the user logs in to Data Analyzer. they cannot change the color scheme assigned to them. Adding Data Restrictions to a User Account You can restrict access to data based on user accounts. Titles do not affect roles or Data Analyzer privileges.

reports. and schedules. Use data restrictions to restrict users or groups from accessing specific data when they view reports. you determine which users and groups can access particular attribute values. When you create data restrictions. You can assign the following types of access permissions to repository objects: ♦ ♦ Read. template dimensions. Use access permissions to restrict access to a particular folder or object in the repository. Allows you to view a folder or object. Write. ♦ When you create an object in the repository. dashboards. Restrict user and group access to folders. or Change Access permission on that object. attributes. Also allows you to create and edit folders and objects within a folder. Write. Setting Access Permissions Access permissions determine the tasks you can perform for a specific repository object. Data Analyzer does not display restricted data associated with those values.CHAPTER 3 Setting Permissions and Restrictions This chapter includes the following topics: ♦ ♦ ♦ Overview. 13 Restricting Data Access. By customizing access permissions on an object. 13 Setting Access Permissions. Allows you to edit an object. When a user with a data restriction runs a report. Restrict access to data in fact tables and operational schemas using associated attributes. 16 Overview You can customize Data Analyzer user access with the following security options: ♦ Access permissions. you determine which users and groups can Read. When you set access permissions. 13 . metrics. every user has default Read and Write permission on that object. you determine which users and groups have access to folders and repository objects. Delete. Data restrictions.

Find > Public Folders > folder name Find > Personal Folder > folder name Find > Public Folders > report name Find > Personal Folder > report name Find > Public Folders > composite report name Find > Personal Folder > composite report name Find > Public Folders > dashboard name Find > Personal Folder > dashboard name Administration > Schema Design > Schema Directory > Metrics folder > metric folder name Administration > Schema Design > Schema Directory > Attributes folder > attribute folder name Administration > Schema Design > Schema Directory > Template Dimensions folder > template dimensions folder name 14 Chapter 3: Setting Permissions and Restrictions . Setting access permissions for a composite report determines whether the composite report itself is visible but does not affect the existing security of subreports... use exclusive access permissions. a composite report might contain some subreports that do not display for all users. For example. Permit access to the users and groups that you select. you can override existing access permissions on all objects in the folder. You can also permit additional access permissions to selected users and groups. To grant more extensive access to a user or group.. including subfolders. Therefore. Allows you to delete a folder or an object from the repository. Data Analyzer grants Read permission to every user in the repository. you can grant the Analysts group inclusive access permissions to delete a report. By default. Navigate to a repository object you want to modify. grant the Sales group inclusive write permission to edit objects in the folder. you can use exclusive access permissions to restrict the Vendors group from viewing sensitive reports. use inclusive access permissions. To set access permissions: 1. then set the access permissions for the user you select. Content folder in Public Folders Content folder in Personal Folder Report in Public Folders Report in Personal Folder Composite Report in Public Folders Composite Report in Personal Folder Public Dashboard Personal Dashboard Metric Folder Attribute Folder Template Dimensions Folder Click. The following table shows how to navigate to the repository object you want to modify: To set access permissions on. If you have reports and shared documents that you do not want to share. You can completely restrict the selected users and groups or restrict them to fewer access permissions. Use the following methods to set access permissions: ♦ ♦ Inclusive. you can select Read as the default access permission for a folder. Exclusive. save them to your Personal Folder or your personal dashboard. To grant access permissions to users. Allows you to change the access permissions on a folder or object. search for the user name. exclusive. For example. Note: Any user with the System Administrator role has access to all Public Folders and to their Personal Folder in the repository and can override any access permissions you set. Use the General Permissions area to modify default access permissions for an object. and default access permissions to create comprehensive access permissions for an object. Users or groups must also have permissions to view individual subreports.♦ ♦ Delete. You can use a combination of inclusive. Restrict access from the users and groups that you select. To restrict the access of specific users or groups. For example. Change permission.. When you modify the access permissions on a folder. and use an exclusive Read permission to deny an individual in the Sales group access to the folder.

Select the access permissions you want to include or exclude... If you are editing access permissions on a folder.To set access permissions on.. skip to step 4. The Access Permissions page appears. 5. click No to prevent all repository users from receiving default access permissions. If you are editing access permissions on an item. 7. The Query Results field displays groups or users that match the search criteria. Select the group or user in the Query Results field. Setting Access Permissions 15 . Administration > Schema Design > Schema Directory > Metrics Folder > metric folder name > metric name Administration > Schema Design > Schema Directory > Attributes folder > attribute folder name > attribute name Administration > Schema Design > Schema Directory >Template Dimensions folder > template dimension folder name > template dimension name Administration > Scheduling > Time-Based Schedules > timebased schedule name Administration > Scheduling > Event-Based Schedules > eventbased schedule name Administration > Schema Directory > Filtersets > filterset name Time-Based Schedule Event-Based Schedule Filterset 2. Refine the selection by choosing the search criteria for the group or user. 9. Only those subreports where a user or group has access permissions display in a composite report. If you click Yes. 4. You can also select Replace Permissions on All Items in Folder to apply access permission changes to the reports and shared documents in the folder. Note: Permissions set on composite reports do not affect permissions on the subreports. 6. -orClick Exclude to exclude the user or group from the access permissions you select. Click the Permissions button ( ) for the repository object. The object name appears in quotes. From the General Permissions area. 8. You can select groups or users by criteria such as name or department. Metric Attribute Template Dimension Click. Click Yes to allow all users to receive the default access permissions you select. Click Make a Selection to search for a group or user. you can select Replace Permissions on Subfolders to apply access permission changes to all subfolders. Click Include to include the user or group in the access permissions you select.. 3. such as a report or shared document. set the default access permissions.

Data Analyzer displays a minus sign (-) next to users or groups you exclude. They cannot see sales data for western or southern regions. unless restricted below. By default. you specify the users or groups to be restricted. This allows you to make the data restriction as specific as required. You can apply the data restriction to a single fact table or operational schema or to all related data in the repository. Data Analyzer applies the data restrictions in the order in which they appear in the Created Restrictions task area. When you create a data restriction. You can create data restrictions using one of the following methods: ♦ Create data restrictions by object. a Data Restrictions button appears in the report. Use this method to apply multiple data restrictions to the same user or group or to restrict all data associated with specified attribute values. If you have multiple data restrictions. the following condition allows users to view data from every March and from the entire year of 2007: IN March OR IN 2007 16 Chapter 3: Setting Permissions and Restrictions . Create data restrictions to keep sensitive data from appearing in reports. they view sales data for their region only. Create data restrictions by user or group. Everyone has Read permission on the Sales folder. Access the fact table or operational schema that contains the metric data you want to restrict and specify the associated attributes for which to restrict the metric data. Corporate Sales group granted additional write permission. you can create a data restriction that restricts the Northeast Sales group to sales data for stores in their region. Select the fact table or operational schema that contains the metric data you want to restrict and specify the associated attributes for which to restrict the metric data. Data Analyzer uses the AND operator to apply all restrictions. In this mode. Red text and a minus sign indicate that the user Hansen is not permitted to read the Sales folder. ♦ If you have multiple data restrictions. When a report contains restricted data. Data Analyzer displays the data restrictions in simple grouping mode. For example. In the advanced grouping mode. For example. 10. use the OR or AND operator to group the data restrictions. When users in the Northeast Sales group run reports that include the SALES fact table and Region attribute. you can create a complex expression with nested conditions. Use this method to apply the same data restriction to more than one user or group. Access the user or group you want to restrict. Restricting Data Access You can restrict access to data associated with specific attribute values. Click OK to save the access permissions settings. You can apply the data restriction to any user or group in the repository.

Using Global Variables You can use global variables when you define data restrictions. For example. You can restrict access to data in the following objects: ♦ ♦ Fact tables Operational schemas You cannot create data restrictions for hierarchical schemas.. Data Analyzer joins the two restrictions and returns no data: Region IN ‘West’ AND Region NOT IN ‘West’ When a user belongs to more than one group. if the user has the restriction Region IN ‘West’ and the user’s group has the restriction Region NOT IN ‘West’.You can also use parentheses to create more complex groups of restrictions... Understanding Data Restrictions for Multiple Groups A restricted user assigned to a restricted group is subject to both individual and group restrictions. Restricting Data Access 17 . When you use a global variable in a data restriction. Data Analyzer updates the data restriction when you update the global variable value.. For example. Both a group and its subgroup Example If Group A has the following restriction: Region IN ‘East’ And Subgroup B has the following restriction: Category IN ‘Women’ Data Analyzer joins the restrictions with AND: Region IN ‘East’ AND Category IN ‘Women’ Two groups that belong to the same parent group OR operator If Group A has the following restriction: Region IN ‘East’ And Group B has the following restriction: Category IN ‘Women’ Data Analyzer joins the restrictions with OR: Region IN ‘East’ OR Category IN ‘Women’ Restricting Data Access by Object Create data restrictions by object when you want to apply the restriction to more than one user or group or to create more than one data restriction for the object. Data Analyzer joins the restrictions with the AND operator. you can group three data restrictions: Region NOT IN ‘North’ AND (Category IN ‘Footware’ OR Brand IN ‘BigShoes’) In the above example. Data Analyzer handles data restrictions differently depending on the relationship between the two groups. Also. The following table describes how Data Analyzer handles multiple group situations: Data Analyzer joins data restrictions with. Data Analyzer allows users to view data which is not included in the North region and which is in either the Footware category or has the BigShoes brand. you cannot create data restrictions on fact tables or operational schemas using CLOB attributes. AND operator A user who belongs to.

If you can create more than one data restriction. Fact Table Operational Schema Click.. The Attribute Selection window appears. 5. To create a data restriction for a user. The Select Group or User window appears. the group search option appears. CLOB attributes are not available for use in data restrictions. Or. search for a user or group. a list of available groups appears. In the Create Restriction task area. 6.. In advanced mode. Click Select a Group/User. If a global variable contains the attribute values you want to use. you can adjust the order of the restrictions and the operators to use between restrictions. 11. or you can search for specific values and Ctrl-click to select more than one. select an operator. Use the Basic or Advanced mode. To create data restrictions for. Data Analyzer displays buttons for adding numbers and operators to the SQL query for the data restriction. Navigate to the attribute you want and select an attribute. Data Analyzer displays the attributes for the object in the Attribute Selection window. Click Find. 18 Chapter 3: Setting Permissions and Restrictions . to create more restrictions for the same user or group. 9. Recently-used attributes appear in the list. You can select attribute values from a list. Navigate to the object you want to restrict. you can select a global variable. and then click the buttons to add numbers or operators to the SQL query. click Advanced in the Created Restrictions task area. If you select Group and the number of groups is less than 30. 10. You can also manually enter attribute values. select User. If the number of groups is 30 or more. To create a data restriction for a group. click Select Other Attributes. 3. 8. Click the Data Restrictions button ( The Data Restrictions page appears. Click within the SQL query. 7. Administration > Schema Design > Analytic Schemas > Show Fact Tables Administration > Schema Design > Operational Schemas 2. Enter attribute values. enter it in the User field. 12.. The data restriction appears in the Created Restrictions task area. Data Analyzer displays the SQL query for the restriction in advanced mode. Use the asterisk or percent symbols as wildcard characters. Select the user or group you want to restrict and click OK. 4. click Advanced. If you select User and you know the user name you want to restrict.To create data restrictions by object: 1. From the condition list. Click Add. select Group. you can edit the SQL query for a restriction. To browse or find other attributes. described in steps 7 to 11. To adjust the restrictions. select an attribute from the attribute list. ) of the object you want to restrict. To view the SQL query for the restriction..

For example. Click OK to save the changes. Also. Recently-used attributes appear in the list. you can create a single data restriction to restrict all sales and salary information from Europe. Data Analyzer displays all attribute folders for the object in the Attribute Selection window. select All Schemas. 5. Applied restrictions appear in the Current Data Restrictions area. click Cancel. Navigate to the attribute you want and select an attribute. To create data restrictions for users.In advanced mode. click Apply Restrictions. Click the appropriate list to group the restrictions. You cannot create data restrictions for hierarchical schemas. select an attribute from the attribute list. 14. if the Region attribute is associated with both the Sales fact table and Salary fact table. To select all schemas. 2. To browse or find an attribute. 13. Restricting Data Access by User or Group Edit a user or group to restrict data when you want to create more than one restriction for the user or group. Click the Data Restrictions button ( The Data Restrictions page appears. click Administration > Access Management > Groups. When the attribute is associated with other fact tables or operational schemas in the repository. click the Remove button. To remove a data restriction. The Attribute Selection window appears. ) of the user or group profile you want to edit. When you have completed adding data restrictions for the user or group. Then click Groups to display all groups. Restricting Data Access 19 . click Administration > Access Management > Users. When you edit a user or group. In the Create Restriction task area. 15. Click to add left parenthesis. Data restrictions limit the data that appears in the reports. you can create data restrictions for metrics in any fact table or operational schema. Click to add right parenthesis. 4. CLOB attributes are not available for use in data restrictions. select an operator. -orTo create data restrictions for groups. you cannot create data restrictions on fact tables or operational schemas using CLOB attributes. You can restrict data in a single fact table or operational schema for an associated attribute. From the condition list. 3. Hierarchical schemas are not available for use in data restrictions. Data Analyzer displays lists for adding parentheses and operators. Select a schema from a list of available schemas. The page shows a list of fact tables and operational schemas tables. Click to add operators. you can restrict all data related to the attribute values you select. This applies the data restriction to all data in the repository associated with the attribute you choose. Click to change the order of the restrictions. To remove all data restrictions. click Select Other Attributes. To create data restrictions for users or groups: 1.

If you create more than one data restriction. Use the Basic or Advanced mode. In advanced mode. You can also manually enter attribute values. the Created Restrictions task area displays lists for adding parentheses and operators. click Advanced in the Created Restrictions task area. 20 Chapter 3: Setting Permissions and Restrictions . Click Add. To remove all data restrictions. If a global variable contains the attribute values you want to use. To view the SQL query for the restriction. Data Analyzer displays buttons for adding numbers and operators to the SQL query for the data restriction. 12. You can select attribute values from a list. Click OK to save the changes. 8. to create more restrictions for the same user or group. click Advanced. click Apply Restrictions. operators. you can edit the SQL query for a restriction. click the Remove button. 7. you can adjust the order of the restrictions and the operators to use between restrictions. Click the appropriate list to group the restrictions. To adjust the restrictions. In advanced mode. To remove a data restriction. Click to change the order of the restrictions. Data Analyzer displays the SQL query for the restriction in advanced mode. Applied restrictions appear in the Current Data Restrictions area. The data restriction appears in the Created Restrictions task area. 10. Click to add right parenthesis. click Cancel. When you have completed adding data restrictions for the user or group. and then click the buttons to add numbers or operators to the SQL query. 11. Click to add left Click to add parenthesis. or you can search for specific values and Ctrl-click to select more than one.6. Enter attribute values. Click within the SQL query. 9. you can select a global variable. described in steps 3 to 8.

29 Overview A time-based schedule updates reports based on a configured schedule. it runs each report attached to the schedule. Updates report data on a regular cycle. create a single-event schedule for December 2. You can configure the following types of time-based schedules: ♦ Single-event schedule. You can attach any cached report to a time-based schedule. date. but do not know when other updates occur. 23 Managing Reports in a Time-Based Schedule. 22 Managing Time-Based Schedules. 25 Using the Calendar. Create a single-event schedule for a one-time update of the report data.CHAPTER 4 Managing Time-Based Schedules This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. Create a recurring schedule to update report data regularly. Attach reports to the time-based schedule as tasks. Create a time-based schedule. To use a time-based schedule. 2. such as once a week or on the first Monday of each month. Configure the start time. Attach a report to the time-based schedule when you create or edit the report. if you know that the ♦ 21 . 29 Defining a Holiday. and repeating option of the schedule when you create or edit a time-based schedule. You might use a recurring schedule to run reports after a regularly scheduled update of the data warehouse. 21 Creating a Time-Based Schedule. Recurring schedule. 29 Monitoring a Schedule. complete the following steps: 1. 28 Defining a Business Day. if you know that the database administrator will update the data warehouse on December 1. Attach imported cached reports to tasks from the time-based schedule. For example. When Data Analyzer runs a time-based schedule. For example. Updates report data only on the configured date.

Use this setting to schedule recurring updates of report data. Date the schedule initiates. Repeat Every (Monday/Tuesday/Wednesday/Thursday/Friday /Saturday/Sunday) 22 Chapter 4: Managing Time-Based Schedules . Enter the following information: Field Name Description Name of the time-based schedule. a weekend or configured holiday. Week. Time the schedule initiates. weekly. If a scheduled run falls on a non-business day. Recurring schedules can repeat every minute. Data Analyzer waits until the next scheduled run to run attached reports. and the following special characters: \/:*?“<>|‘&[] Description of the time-based schedule. tab. Hour. Monitor existing schedules with the Calendar or the Schedule Monitor. (noon). Repeats each week on the specified day(s). select one of the following repeat options: Field Repeat Every (Number) (Minute/Hour/Day/Week/Month/Year) Description Repeats every specified number of units of time. The Properties page appears. When selected.data warehouse is updated the first Friday of every month. The Schedule Monitor provides a list of the schedules currently running reports. For a single-event schedule. or hourly. the schedule runs reports on business days only. You can set up business days and holidays for the Data Analyzer Calendar. Default is the current date on Data Analyzer. select Do Not Repeat. To create a time-based schedule: 1.m. create a time-based schedule to update reports on the second Monday of every month. Description Business Day Only Start Date Start Time 3. Select minutes in increments of five. The Calendar provides daily. weekly. The name can include any character except a space. newline character. Single-event schedules run tasks once. 2. For a repeating schedule. or Year as a unit of time. If you want to update reports when a PowerCenter session or batch completes. Select a repeat option. or monthly views of all the time-based schedules in the repository. Default is 12:00 p. or quarterly. monthly. daily. you can create indicators and alerts for the reports. Day. Creating a Time-Based Schedule You can create single-event or recurring schedules to run reports as tasks. After you attach reports to a time-based schedule. Use this setting to schedule weekly updates of report data. Month. You can select Minute. you can create an event-based schedule. Click Administration > Scheduling > Time-Based Schedules > Add.

Default is the current date on Data Analyzer.Field Repeat the (First/Second/Third/Fourth) (Monday/Tuesday/Wednesday/Thursday/Friday /Saturday/Sunday) of every (Month/Year) Repeat on (Number) of days from the (Beginning of/End) of the (First/Second/Third Month) of each Quarter 4. Default is Always. Managing Time-Based Schedules After you create a time-based schedule. To edit a time-based schedule: 1. The Properties page appears. Edit schedule properties if necessary. You can also remove reports or change the order in which they run. Schedule repeats until the date you specify. View or clear the schedule history. Managing Time-Based Schedules 23 . Stop the schedule immediately. Select the repeat condition: Field Always Until (Month) (Day) (Year) Description Schedule repeats until disabled or deleted from the repository. Start the schedule immediately. you can attach reports to the schedule. it runs each attached report. The Time-Based Schedules page appears. 3. 5. and then click OK. the change impacts all attached reports and alerts. Use this setting to schedule monthly or yearly updates of report data. 2. Repeats every specified number of days from the beginning or end of the specified month. Editing a Time-Based Schedule After you create a time-based schedule. You can complete the following tasks for a time-based schedule: ♦ ♦ ♦ ♦ ♦ ♦ Edit a schedule. Click Tasks to remove reports from the schedule. Use this setting to schedule quarterly updates of report data. Click OK. Click the name of the schedule you want to edit. Click Administration > Scheduling > Time-Based Schedules. Disable the schedule. you can edit schedule properties. Edit schedule access permissions. When Data Analyzer runs a time-based schedule. Description Repeats on the specified day of the week of every month or year. When you update the schedule of a time-based schedule. You can attach any cached report to a time-based schedule. 4.

The date and time Data Analyzer started running the schedule. The schedule name appears in parentheses. click Clear. modify the schedule. or change access permissions to the schedule. Status. 3. The Properties page appears. End time.Editing Access Permissions for a Time-Based Schedule Access permissions determine which users and groups can attach reports to the schedule. Each time-based schedule has a history containing the following information: ♦ ♦ ♦ Start time. click the Permissions button. To view or clear the history of a time-based schedule: 1. or the number of recurring errors during the run. You can change the access permissions for a schedule to protect the security of the schedule. the number of successfully completed schedule runs. To set access permissions. Click History. Click OK. You might clear a schedule history at the end of a quarter or to save space in the repository. Click Administration > Scheduling > Time-Based Schedules. The Time-Based Schedules page appears. The date and time Data Analyzer stops running the schedule. you can determine how long all tasks attached to the schedule take to update. Click to change access permissions. 5. By default every user with the appropriate privileges can edit a schedule. You might start a time-based schedule immediately to test attached reports. Select the schedule you want to view. 4. Viewing or Clearing a Time-Based Schedule History You can view the history of a time-based schedule. 24 Chapter 4: Managing Time-Based Schedules . 2. You might also start the schedule if errors occurred during the previously scheduled run. When you view schedule histories. The Schedule History page appears. To clear the history of the schedule. You can also clear the history of a schedule. Starting a Time-Based Schedule Immediately You can start a time-based schedule immediately instead of waiting for its next scheduled run. Lists whether the schedule or task completed successfully or the number of errors that occurred.

3. click Run Now. Removing a Time-Based Schedule You can remove time-based schedules from the repository. Data Analyzer starts the schedule and runs the attached reports. Data Analyzer recommends that you reassign all tasks attached to the schedule. Click Administration > Scheduling > Time-Based Schedules. You might disable a schedule when it has no attached reports or when the update of source data is temporarily interrupted. You can attach any cached report to a time-based schedule. you can enable the schedule. For the time-based schedule you want to start. When you want to enable the schedule again. Click Administration > Scheduling > Time-Based Schedules. Click OK. 2. To remove a time-based schedule: 1. View a list of attached reports. The status of the schedule changes to Disabled. View task properties. 2. see “Stopping a Schedule” on page 30. aborting all attached reports. When Data Analyzer runs a time-based schedule. Managing Reports in a Time-Based Schedule After you create a time-based schedule. Managing Reports in a Time-Based Schedule 25 .To start a time-based schedule immediately: 1. Disabling a Time-Based Schedule You can disable a time-based schedule when you do not want it to run. Stopping a Time-Based Schedule Immediately You can stop a time-based schedule immediately. Click the Enabled button for the schedule you want to disable. To disable a time-based schedule: 1. The Time-Based Schedules page appears. For more information. click the Disabled button. Click the Remove button for the schedule you want to delete. 2. You can complete the following schedule-related tasks for a report: ♦ ♦ ♦ ♦ ♦ Attach a report to a time-based schedule. Click Administration > Scheduling > Time-Based Schedules. you can attach reports to the schedule. it runs each attached report. Remove a report from a time-based schedule. When you want the schedule to resume. Before you remove any schedule from the repository. View or clear a task history. You can stop a schedule immediately when you need to restart the server.

the report schedule must update more often than the alert schedule updates. and change the scheduling options. 5. Attaching Imported Cached Reports to a Time-Based Schedule When you import cached reports to the repository. Click the time-based schedule that you want to use. Viewing Attached Reports All reports that are attached to a time-based schedule display as a list of tasks for the schedule. Data Analyzer attaches the rules to the schedule but does not display the rules on the list of tasks for the schedule. Save an existing report as a cached report. You can attach imported cached reports to time-based or event-based schedules.Attaching Reports to a Time-Based Schedule You can attach a report to a time-based schedule using one of the following methods: ♦ ♦ ♦ Save a new report as cached. Although the rules do not display on the Tasks page for the schedule. but not to an eventbased schedule. The report appears as an item on the task list. Select Save As on an existing report. 26 Chapter 4: Managing Time-Based Schedules . Click Tasks. Data Analyzer runs the reports concurrently. You can attach multiple reports to a single schedule. Select a schedule and use the add task option to attach multiple imported cached reports to an existing schedule. You can view these tasks on the Tasks page for the schedule. Add an imported report to a schedule. You must attach the imported reports individually. you cannot attach multiple reports. The Add button appears only when you have unscheduled imported reports in the repository. Select the imported reports that you want to add to the schedule. 4. attach a small number of reports to a schedule. you must attach the reports during the same Data Analyzer session. You can attach each imported report individually or attach multiple imported reports from a list to a single schedule. Click Add. You must attach any cached reports that you import to a schedule. When a user selects broadcast or an alert rules for a time-based schedule. Please assign the reports to schedules immediately. Click Administration > Scheduling > Time-Based Schedules. You can attach reports that have alerts on a predefined schedule to a time-based schedule. If you want to add all available imported reports as a task for the schedule. Set up multiple schedules to run a large number of reports. Data Analyzer applies the rules when it runs the report on the time-based schedule. 3. If you attach a report that has alerts on a predefined schedule to a time-based schedule. 2. If the session expires or you log out before attaching multiple reports from the import list. To make troubleshooting easier. 6. Select the schedule option when you save a new report to the repository. The Imported Scheduled Reports window appears. If you attach multiple reports to a schedule. Click Apply. the following message appears: Some of the imported reports must be put on schedules. To attach multiple reports from the list. The list of the tasks attached to the schedule appears. select the All check box next to Select Reports. To attach an imported cached report to a time-based schedule: 1.

5. Click the name of the schedule that runs the report. The Time-Based Schedules page appears. 6. Managing Reports in a Time-Based Schedule 27 . You can also clear the history of a report. To clear the task history. Click OK to close the Task Properties page. You can clear a task history at the end of a quarter or to save space in the repository. All attached reports display. The Properties page appears. Viewing Task Properties You can view the task properties for any report attached to a time-based schedule. To view task properties: 1. Click Administration > Scheduling > Time-Based Schedules. You can view a task history to compare the number of successful runs on different schedules. 3. Click the name of the schedule that runs the report. Click the name of the report. 3. the number of successfully completed runs.To view a report attached to a time-based schedule: 1. 2. click Clear. Click the schedule you want to view. 5. Remove a report when you plan to disable the schedule or when the report requires a new update strategy. Viewing or Clearing a Task History You can view a task history for reports attached to time-based schedules. you must attach it to another schedule to ensure it updates in a timely manner. Click Tasks. and then click OK. To view or clear a task history: 1. 4. View report histories to determine how long the report takes to update. 2. 2. 3. 4. Click Tasks. You cannot modify the task properties. When you remove a task. To return to Task Properties. 7. Click Administration > Scheduling > Time-Based Schedules. click OK. The Task Properties page appears. Click Tasks. Click Administration > Scheduling > Time-Based Schedules. or recurring errors when running the report. The Task Properties page appears. Click History. Click the name of the report. Removing a Report from a Time-Based Schedule You can remove a report from a time-based schedule.

Navigating the Weekly View The Weekly view opens to the current week by default. week. select a different date or month in the calendar. To access a Daily view. Click Remove. 5. Navigating the Monthly View The Monthly view opens to the current month by default. and then click OK. select the check box in the title bar next to Name. To access a Weekly view. The Calendar lists schedules by day. 3. To view a different date. The Calendar appears. The Weekly view displays all time-based schedules for the week. The Calendar recognizes leap years. Select the check box for the report you want to remove. Use the left and right arrows to navigate to the previous and following weeks. 2. To access a Daily view. If you want to remove all attached reports. Click the name of the schedule you want to edit. Using the Calendar Use the Calendar in the Scheduling section to view all enabled time-based schedules in the repository. 2. respectively. respectively. or month. weekly. click a date. respectively. The Daily view displays the current day and organizes the time-based schedules for the current day by hour. Click Tasks. Navigating the Daily View The Calendar opens to the Daily view by default. Navigating the Calendar The Calendar provides daily. click a week. The Properties page appears. The Monthly view displays all time-based schedules for the month. Use the left and right arrows to navigate to the previous and next day. Click Weekly or Monthly to change the view of the Calendar. The Time-Based Schedules page appears. 28 Chapter 4: Managing Time-Based Schedules .To remove a report from a time-based schedule: 1. Use the left and right arrows to navigate to the previous and following months. and monthly views. 4. To view the Calendar: 1. Click Administration > Scheduling > Calendar. You can navigate from one view to another. click the specific date. Click Administration > Scheduling > Time-Based Schedules. The default Calendar display is a view of the current day.

You might check the Schedule Monitor before you restart Data Analyzer to make sure no schedules are running. Data Analyzer runs the reports on the next scheduled day. Click Administration > Scheduling > Holidays. View all configured holidays on the Holidays page. 2. If the schedule falls on a nonbusiness day. If March 1 falls on a Sunday. April 1. Click Administration > Scheduling > Business Days. the configured business days are Monday through Friday. 4. and configure the schedule to run only on business days. Data Analyzer postpones the schedule to run attached reports on the next scheduled day. Click Apply. Click Add. like a weekend or holiday. date. The Holidays page appears. You might also use the Schedule Monitor to verify whether Data Analyzer runs reports at the scheduled time. Monitoring a Schedule The Schedule Monitor provides a list of all schedules that are currently running in the repository. For example. Defining a Business Day 29 . Select the days you want to define as business days. Enter the name. You create a schedule to run reports on the first of the month. 3. The Business Days page appears. After you define business days. to run the schedule. The Holiday Properties page appears. 2. Defining a Holiday You can define holidays for the Data Analyzer Calendar. The default business days are Monday through Friday.Defining a Business Day You can define business days for the Data Analyzer Calendar. To define business days: 1. When a schedule falls on a holiday. Time-based schedules that are not configured to run only on business days still run on configured holidays. 3. Business days are the days Data Analyzer treats as regular working days. there are no configured holidays. Data Analyzer waits until the next scheduled day. and a brief description of the holiday. The business day setting overrides all other recurring schedule settings you create. You can change these business days to fit your work schedule. Click OK. Time-based schedules configured to run reports only on business days do not run on holidays. Data Analyzer treats holidays as non-business days. you can create time-based schedules that run only on those days. To define a holiday: 1. Clear the days you do not want defined as business days. By default.

To stop a running schedule: 1. 3. The Schedule Monitor lists all currently running schedules. Click Administration > Scheduling > Schedule Monitoring. click Administration > Scheduling > Schedule Monitoring.To monitor a schedule. Click OK. 30 Chapter 4: Managing Time-Based Schedules . 2. You might stop a schedule when you need to restart the server or when a problem arises with source data. Data Analyzer displays schedules that are currently running. Click Remove to stop a running schedule. Stopping a Schedule You can stop a running schedule and all attached reports through the Schedule Monitor.

For more information. You cannot use the PowerCenter Integration utility with a time-based schedule. If the PowerCenter Integration utility is set up correctly. Updating Reports When a PowerCenter Session Completes When you create a Reporting Service in the PowerCenter Administration Console.CHAPTER 5 Managing Event-Based Schedules This chapter includes the following topics: ♦ ♦ ♦ ♦ Overview. 33 Managing Reports in an Event-Based Schedule. You can create indicators and alerts for the reports in an event-based schedule. 35 Overview PowerCenter Data Analyzer provides event-based schedules and the PowerCenter Integration utility so you can update reports in Data Analyzer based on the completion of PowerCenter sessions. Use the PowerCenter Integration Utility in PowerCenter” on page 33. Create an event-based schedule and attach cached reports to the schedule. You can monitor event-based schedules with the Schedule Monitor. To update reports in Data Analyzer when a session completes in PowerCenter. 31 Updating Reports When a PowerCenter Session Completes. 31 . 31 Managing Event-Based Schedules. see “Step 1. PowerCenter installs the PowerCenter Integration utility. Create an Event-Based Schedule” on page 32. complete the following steps: 1. Data Analyzer runs each report attached to the eventbased schedule when a PowerCenter session completes. Configure a PowerCenter session to call the PowerCenter Integration utility as a post-session command and pass the event-based schedule name as a parameter. The Schedule Monitor provides a list of the schedules currently running reports. For more information. see “Step 2. 2.

properties file to update reports in Data Analyzer. The PowerCenter Integration utility creates a log file when it runs after the PowerCenter session completes. When you create a Reporting Service.sh Windows: notifyias.bat Back up the notifyias file before you modify it. you can attach it to a cached report when you save the report. Before you run the PowerCenter Integration utility. Click Add.properties file to point to the correct instance of the Reporting Service. Click OK. 3. The PowerCenter Integration utility considers the settings in the notifyias. Select the cached report option and a specific schedule when you save a new report to the repository. Step 1. 3. complete the following steps: 1. The Add an Event-Based Schedule page appears. 32 Chapter 5: Managing Event-Based Schedules . The logfile.PowerCenter installs a separate PowerCenter Integration utility for every Reporting Service that you create. PowerCenter sets the properties in the notifyias. For example. To create an event-based schedule: 1.properties file contains information about the Reporting Service URL and the schedule queue name.properties file in the notifyias-<Reporting Service Name> folder and set the logfile. 2. Create an Event-Based Schedule To run reports in Data Analyzer after a session completes in PowerCenter. 2. Click Administration > Scheduling > Event-Based Schedules. 4. The Event-Based Schedules page appears. After you create the event-based schedule. the notifyias folder would be notifyias-DA_Test. The notifyias. Set the JAVA_HOME environment variable to the location of the JVM. create an event-based schedule in Data Analyzer and attach the reports that you want to run after the PowerCenter session completes. Attaching Reports to an Event-Based Schedule You can attach a report to an event-based schedule with one of the following methods: ♦ Save a new report as a cached report. Open the notifyias file in a text editor: UNIX: notifyias. You do not need to provide information about the PowerCenter session you want to use.location property to the location and the name of the PowerCenter Integration utility log file. Run the PowerCenter Integration utility to update reports in Data Analyzer when a session completes in PowerCenter. if you create a Reporting Service and call it DA_Test. you need to provide a name and description of the schedule. Open the notifyias. You can find the PowerCenter Integration utility in the following folder: <PCInstallationfolder>\server\tomcat\jboss\notifyias-<Reporting Service Name> PowerCenter suffixes the Reporting Service name to the notifyias folder. Creating an Event-Based Schedule When you create an event-based schedule. Enter a name and description for the schedule.location property determines the location and the name of the log file.

bat Event-BasedScheduleName Use the following shell command syntax for PowerCenter installed on UNIX: notifyias. Start a schedule immediately. You can set up the post-session command to send Data Analyzer notification when the session completes successfully. attach a small number of reports to a schedule. To make troubleshooting easier. you need to prefix the utility file name with the file path. Set up multiple schedules to run a large number of reports. You can also run the PowerCenter Integration utility as a command task in a PowerCenter workflow. If you want to run the PowerCenter Integration utility after all other tasks in a workflow complete. If you attach multiple reports to a schedule. and specify the name of the event-based schedule that you want to associate with the PowerCenter session. you must configure the PowerCenter session to call the PowerCenter Integration utility as a post-session command.sh Event-BasedScheduleName Event-BasedScheduleName is the name of the Data Analyzer event-based schedule that contains the tasks you want to run when the PowerCenter session completes. Step 2. Disable a schedule. see the PowerCenter Workflow Administration Guide. For more information about configuring post-session commands. When you use the PowerCenter Integration utility in the post-session command.♦ Save an existing report as a cached report. Data Analyzer then connects to the PowerCenter data warehouse to retrieve new data to update reports. If the system path does not include the path of the PowerCenter Integration utility. create an event-based schedule as outlined in the previous step. Data Analyzer runs the reports concurrently. Use the PowerCenter Integration Utility in PowerCenter Before you can use the PowerCenter Integration utility in a PowerCenter post-session command. Managing Event-Based Schedules 33 . Managing Event-Based Schedules You can perform the following tasks to manage an event-based schedule: ♦ ♦ ♦ ♦ ♦ ♦ ♦ Edit a schedule. Edit schedule access permissions. you need to navigate to the correct notifyias-<Reporting Service name> folder. Stop a schedule immediately. View or clear the schedule history. Editing an Event-Based Schedule After you create an event-based schedule. you can edit its name and description. Select Save As on a report. you can run it as the last task in the workflow. or the PowerCenter Integration utility. Remove a schedule. In the PowerCenter Workflow Manager. You can attach multiple reports to a single schedule. then change the scheduling options. Use the following post-session command syntax for PowerCenter installed on Windows: notifyias. PowerCenter workflows.

Click Administration > Scheduling > Event-Based Schedules. End time. Click the schedule you want to view. click Clear. the system administrator and users with the Set Up Schedules and Tasks privilege and Write permission on the schedule can edit an event-based schedule. or change access permission for the schedule. Editing Access Permissions for an Event-Based Schedule Access permissions determine which users and groups can attach reports to the schedule. If you want to view the history of the schedule. Click OK. To view an event-based schedule histor y: 1. The Event-Based Schedules page appears. By default. You might start the schedule if errors occurred during the last run of the schedule. Status. click History. you can change the access permissions for the schedule. click Tasks. 5. Edit the name or description of the event-based schedule. If you want to view the reports assigned as tasks to the schedule. Starting an Event-Based Schedule Immediately You can start an event-based schedule immediately instead of waiting for the related PowerCenter session to complete. Click Administration > Scheduling > Event-Based Schedules. Click History. You might start an event-based schedule immediately to test attached reports and report alerts. click the Permissions button. 34 Chapter 5: Managing Event-Based Schedules . The Edit an Event-Based Schedule page appears. View schedule histories to determine how long attached reports take to complete. To secure a schedule. the number of successfully completed runs of the schedule.To edit an event-based schedule: 1. modify the schedule. You can also clear the history of an event-based schedule. The date and time the schedule completes. 4. 3. Viewing or Clearing an Event-Based Schedule History You can view the history of an event-based schedule to see the following information: ♦ ♦ ♦ Start time. 3. The Event-Based Schedules page appears. To clear the schedule history. The Schedule History page appears with the schedule name in parentheses. 2. Lists the successful completion of the schedule or the number of errors that have occurred. To edit access permissions. or the number of recurring errors. 2. 4. Click OK. The date and time Data Analyzer started the schedule. Click the name of the schedule you want to edit. You might clear a schedule history at the end of a quarter or to save space in the repository.

click Run Now. Click the Enabled button for the schedule you want to disable. To enable the schedule again. Managing Reports in an Event-Based Schedule 35 . Click OK. The Event-Based Schedules page appears. You can stop a schedule immediately when you need to restart the server. which stops all attached reports. Data Analyzer starts the schedule and runs the attached reports. reassign all attached reports to another schedule. Click Administration > Scheduling > Event-Based Schedules. see “Stopping a Schedule” on page 30. You might disable a schedule when it has no attached reports or when the update of source data has been interrupted.To start an event-based schedule immediately: 1. Disabling an Event-Based Schedule You can disable an event-based schedule when you do not want it to run. Removing an Event-Based Schedule You can remove event-based schedules from the repository. View task properties. Click Administration > Scheduling > Event-Based Schedules. you can attach any cached reports to the schedule. When you want the schedule to resume. it runs each attached report. To disable an event-based schedule: 1. 3. The Event-Based Schedules page appears. 2. The Status of the schedule changes to Disabled. Stopping an Event-Based Schedule Immediately You can stop an event-based schedule immediately. Managing Reports in an Event-Based Schedule After you create an event-based schedule. Before removing a schedule from the repository. 2. For the event-based schedule you want to start. You can perform the following tasks to manage reports in an event-based schedule: ♦ ♦ ♦ ♦ ♦ View a list of attached reports. Click Administration > Scheduling > Event-Based Schedules. Click the Remove button for the schedule you want to delete. 2. When Data Analyzer runs an event-based schedule. you can enable the schedule. You might want to remove an event-based schedule when the PowerCenter session is no longer valid. For more information. Attach imported cached reports to a schedule. Remove a report from an event-based schedule. View or clear a report history. click Disabled. To remove an event-based schedule: 1.

Viewing or Clearing a Report History You can view a report history for the reports attached to an event-based schedule. Click Administration > Scheduling > Event-Based Schedules. Viewing Task Properties You can view the properties of any report attached to an event-based schedule. Click Tasks. The Event-Based Schedules page appears. 5. Click Administration > Scheduling > Event-Based Schedules. The Task Properties page appears. Click the name of the schedule that runs the report. 6. 3. Click Tasks. To clear the history. To view tasks attached to an event-based schedule: 1. 2. Click the name of the report. and then click OK. The Task Properties page appears. To view or clear a report history: 1. 7. View report histories to determine how long a report takes to update. Click the name of the schedule that runs the report. Click History. 2.Viewing Attached Reports You can view all reports attached to an event-based schedule. Click Tasks. The schedule properties display. 4. the number of successfully completed runs. Click OK. Click the name of the report. Data Analyzer displays the report history. To view task properties: 1. Click the name of the schedule you want to edit. 3. You might want to view a report history to compare the number of successful runs on different schedules. 5. click OK. 4. 36 Chapter 5: Managing Event-Based Schedules . Click Administration > Scheduling > Event-Based Schedules. 3. You can also clear report the history. To return to Task Properties. 2. You might clear history at the end of a quarter or to make space in the repository. Data Analyzer displays all attached reports. click Clear. or recurring errors when running the report.

Click the event-based schedule that you want to use. Please assign the reports to schedules immediately. Managing Reports in an Event-Based Schedule 37 . When you remove a cached report. You must attach each imported cached report to a schedule.Removing a Report from an Event-Based Schedule You can remove a report from an event-based schedule. The Imported Scheduled Reports window appears. You can attach imported reports individually or attach multiple imported reports from a list to a single schedule. 3. The Add button appears only when you have unscheduled imported reports in the repository. Click the name of the schedule you want to edit and then click Tasks. If the session expires or you log out before attaching the reports from the import list. attach it to another schedule to ensure it updates in a timely manner. To attach multiple reports from the list. The list of the tasks assigned to the schedule appears: Appears when imported reports are not yet scheduled. To attach an imported cached report to an event-based schedule: 1. You might want to remove a report when you plan to disable the schedule or when the report requires a new update strategy. Attaching Imported Cached Reports to an Event-Based Schedule When you import cached reports to the repository. If you want to remove all attached reports. You must attach the imported reports individually. To remove a report from an event-based schedule: 1. Click Add. 4. Click Administration > Scheduling > Event-Based Schedules. 2. you must attach them during the same Data Analyzer session. and then click OK. you cannot attach multiple reports. Select the check box for the report you want to remove. You can attach imported cached reports to time-based or event-based schedules. Click to add the reports to existing schedules. Click Administration > Scheduling > Event-Based Schedules. select the check box in the title bar next to Name. 2. Click Tasks. 3. Click Remove. 4. Data Analyzer displays the following message: Some of the imported reports must be put on schedules.

Click Apply. The report appears as an item on the task list. 38 Chapter 5: Managing Event-Based Schedules . Select the reports that you want to add to the schedule. click the All check box. If you want to add all available imported reports to the schedule.5. 6.

You might want to export objects to archive the repository. 39 Exporting a Schema.CHAPTER 6 Exporting Objects from the Repository This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. You can export the following repository objects: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Schemas Time Dimensions Reports Global Variables Dashboards Security profiles Schedules Users Groups Roles 39 . 46 Troubleshooting. 42 Exporting a Report. 40 Exporting a Time Dimension. 42 Exporting a Global Variable. 44 Exporting a Dashboard. 47 Overview You can export repository objects to XML files and import repository objects from XML files. 44 Exporting a Security Profile. You might also want to export and import objects to move Data Analyzer objects from development to production. 45 Exporting a Schedule.

− When exporting a calculated metric. Schedule exporting and importing tasks so that you do not disrupt Data Analyzer users. and other schema objects associated with the metric. Data Analyzer exports the metrics you select. Data Analyzer also exports all fact tables associated with any of the exported metrics. You can also export repository objects using the ImportExport command line utility. usually in the C: drive. and tables in the operational schema and the join expressions for the operational schema tables. including the calculated metric and those used to calculate it. Exporting Metrics and Associated Schema Objects When Data Analyzer exports a metric or schema and the associated objects. Data Analyzer creates an XML file that contains information about the exported objects. for the temporary space typically required when a file is saved. see “Using the Import Export Utility” on page 65. You can export the following metrics and schemas: ♦ ♦ ♦ ♦ Operational schemas or metrics in operational schemas Analytic schemas or metrics in analytic schemas Hierarchical schemas or metrics in hierarchical schemas Calculated metrics Exporting Operational Schemas When Data Analyzer exports a metric from an operational schema. You can view the XML files with any text editor. Data Analyzer also exports all associated metrics that are used to calculate the calculated metric. it exports different objects based on the type of schema you select. If you perform these tasks while users are logged in to Data Analyzer. When you export a schema from the Data Analyzer repository. you can select individual metrics within a schema to export or you can select a folder that contains metrics. Exporting and importing repository objects uses considerable system resources. tables. You can also choose whether to export only metric definitions or to export all metrics. do not modify the XML file created when you export objects. attributes. Exporting Analytic Schemas When exporting a metric from an analytic schema. However. It does not export the definition of the table or schema that contains the metrics or any other schema object associated with the metric or its table or schema. 40 Chapter 6: Exporting Objects from the Repository .When you export the repository objects. Use this file to import the repository objects into a Data Analyzer repository. For more information. attributes. verify that you have enough space available in the Windows temp directory. Any change might invalidate the XML file and prevent you from using it to import objects into a Data Analyzer repository. Exporting Metric Definitions Only When you export only metric definitions. users might experience slow response or timeout errors. it also exports all metrics. Exporting a Schema You can export analytic and operational schemas. When you save the XML file on a Windows machine. Data Analyzer exports the definitions of the following schema objects associated with the metric: ♦ Fact tables associated with the exported metric.

It does not export any associated schema object. you can select Metrics to select all folders and metrics in the list. 2. Dimension tables associated with the exported fact tables. Aggregate fact tables associated with the exported fact tables. select Export Metric Definitions Only. Data Analyzer exports BaseMetric3 and its entire associated operational schema. If you export a calculated metric. Exporting Calculated Metrics Calculated metrics are derived from two or more base metrics from analytic. Select the type of information you want to export. Dimension keys in the exported fact table. You can export the time dimensions separately. If you define a new object in the repository or if you create a new folder or move objects in the Schema Directory. Data Analyzer exports only one definition of the template dimension. For example. To export schema objects: 1. which is calculated from BaseMetric1 and BaseMetric3. Data Analyzer exports the fact table associated with each metric. Base metric 4 (BaseMetric4) is a metric from a different operational schema (OpSch2). Drill paths associated with any of the attributes in the dimension tables. In addition. template. If you export a template dimension table associated with the exported metric. it also exports all metrics and attributes in the hierarchical schema. and snowflake dimension tables associated with the dimension tables. Data Analyzer exports BaseMetric1. Data Analyzer exports all schema objects associated with the metrics in these fact tables. If you export a calculated metric. its associated fact table. Attributes in the exported dimension tables. or template dimensions that you want to export. operational. If you export only a template dimension. Select the folders. Data Analyzer does not export the time dimension. Data Analyzer exports only the template dimension and its attributes. metrics. Base metric 3 (BaseMetric3) is a metric from an operational schema (OpSch1). the changes may not immediately display in the Schema Directory export list. which is calculated from BaseMetric3 and BaseMetric4. and BaseMetric4 and its entire operational schema. which is calculated from BaseMetric1 and BaseMetric2. select Export the Metrics with the Associated Schema Tables and Attributes. Exporting Hierarchical Schemas When Data Analyzer exports a metric from a hierarchical schema.− ♦ ♦ ♦ ♦ ♦ ♦ When exporting a fact table associated with a time dimension. and the schema objects associated with the metric in that fact table. The Export Schemas page displays all the folders and metrics in the Metrics folder of the Schema Directory. To export the metric definitions and associated tables and attributes. To export only metric definitions. You can also export template dimensions separately. you have the following metrics: ♦ ♦ ♦ Base metric 1 (BaseMetric1) and base metric 2 (BaseMetric2) are metrics from fact tables in an analytic schema. Aggregate. 3. In addition. Click Administration > XML Export/Import > Export Schemas. Click Refresh Schema to display the latest list of folders and metrics in the Schema Directory. Exporting a Schema 41 . If you export a calculated metric. Data Analyzer exports BaseMetric3 and its entire operational schema. At the top of the Metrics section. or hierarchical schemas.

4. Click Save. The File Download window appears. You can export multiple reports at once. When exporting cached reports. Data Analyzer exports the time dimension table to an XML file. 5. The Save As window appears. When you export a report. Select the time dimension you want to export. Data Analyzer always exports the following report components: ♦ ♦ ♦ Report table Report charts Filters 42 Chapter 6: Exporting Objects from the Repository . 3. Click Export as XML. The File Download window appears. To export a time dimension table: 1. Exporting a Report You can export reports from public and personal folders. 2. Click Administration > XML Export/Import > Export Time Dimensions. If an XML file with the same name already exists in the directory. 4. Time dimension tables contain date. You can export cached and on-demand reports. Data Analyzer exports the schema to an XML file. 6. 7. 6. Data Analyzer exports all reports in the folder and its subfolders. Click Save. You can also select individual metrics in different folders. Data Analyzer prompts you to overwrite the file or rename the new file. Click Export as XML. Enter a name for the XML file and click Save. Navigate to the directory where you want to save the file. 5.You can select Template Dimensions to select all template dimensions in the list or select a metrics folder to export all metrics within the folder. The Save As window appears. Data Analyzer exports the report data and the schedule for cached reports. Navigate to the directory where you want to save the file.and time-related attributes that describe the occurrence of a metric. Exporting a Time Dimension You can export time dimension tables to an XML file. When you export a folder. Enter a name for the XML file and click Save. The Export Time Dimensions page displays the time dimension tables in the repository.

with the following exceptions: ♦ ♦ ♦ To export an analytic workflow. Click Export as XML. and then click Save. Exported public gauge indicators keep their original owner. Although the global variables are not exported with the report. 2. The File Download window appears. Data Analyzer exports all current data for each component. 7.♦ ♦ ♦ ♦ Calculations Custom attributes All reports in an analytic workflow All subreports in a composite report By default. Data Analyzer also exports the following components associated with reports. Data Analyzer exports the definitions of all selected reports. The Save As window appears. If you create. you can export them separately. 5. 6. Click Save. You can choose not to export any of these components: ♦ ♦ ♦ ♦ ♦ ♦ Indicators Alerts Highlighting Permissions Schedules Filtersets Gauge indicators. Data Analyzer does not export any personal highlighting. or delete a folder or report. From the list of Export Options. Exported personal and public alerts use the state set for all report subscribers as the default alert state. Click Refresh Reports to display the latest list of reports from Public Folders and Personal Folder. Click Administration > XML Export/Import > Export Reports. Exporting a Report 43 . When you export the originating report of an analytic workflow. 3. 8. 4. Alerts. The user who imports the report becomes the owner of the gauge indicator and the gauge indicator becomes personal to that user. Data Analyzer lists the global variables used in the report. Data Analyzer exports all the workflow reports. Highlighting. clear each component that you do not want to export to the XML file. To modify the report components to export. you need to export only the originating report. click Export Options. When you export a report that uses global variables. Select a folder to export all subfolders and reports in the folder. the changes may not immediately display in the report export list. Enter a name for the XML file. modify. Exported public highlighting uses the state set for all users as the default highlighting state. To export a report: 1. Exported personal gauge indicators do not keep their original owner. The Export Report page displays all public and personal folders in the repository that you have permission to access. Select the folders or reports that you want to export. Navigate to the directory where you want to save the file.

You can export more than one dashboard at a time. 2. The Save As window appears. The File Download window appears. 6. 3. Click Administration > XML Export/Import > Export Global Variables. the Export Options button is unavailable. Click Save. The Export Dashboards page appears. Optionally. Click Administration > XML Export/Import > Export Dashboards. Data Analyzer creates one XML file for the global variables and their default values. Navigate to the directory where you want to save the file. select Name at the top of the list to select all the dashboards in the list. To export a dashboard: 1. Select the global variables that you want to export. To export a global variable: 1. Select the dashboards that you want to export. listing all the dashboards in the repository that you can export.Exporting a Global Variable You can export any global variables defined in the repository. listing all the global variables in the repository. Therefore. you cannot select specific components to export. Data Analyzer exports the following objects associated with the dashboard: ♦ ♦ ♦ ♦ ♦ ♦ Reports Indicators Shared documents Dashboard filters Discussion comments Feedback Access permissions Attributes and metrics in the report Real-time objects Data Analyzer does not export the following objects associated with the dashboard: ♦ ♦ ♦ When you export a dashboard. When you export multiple global variables. 44 Chapter 6: Exporting Objects from the Repository . Click Export as XML. 4. 2. Data Analyzer exports the definitions of all selected global variables. You can export any of the public dashboards defined in the repository. 5. Enter a name for the XML file and click Save. The Export Global Variables page appears. Optionally. Exporting a Dashboard When you export a dashboard. select Name at the top of the list to select all the global variables in the list.

Click Administration > XML Export/Import > Export Security Profile. Exporting a User Security Profile You can export a security profile for one user at a time. Click Export from Users. Exporting a Security Profile 45 . Navigate to the directory where you want to save the file. Click Export as XML. Data Analyzer allows you to export one security profile at a time. Data Analyzer exports the security profile definition of the selected user. The Save As window appears. Click Save. and attributes. 4. Enter a name for the XML file and click Save. The File Download window appears. The File Download window appears. 5.3. which include folders. Data Analyzer does not export any object definitions and displays the following message: There is no content to be exported. 6. Exporting a Security Profile Data Analyzer keeps a security profile for each user or group in the repository. reports. To view a list of users on other pages. Enter a name for the XML file and click Save. The Export Security Profile page displays a list of all the users in the repository 3. Data Analyzer exports the definitions of all selected dashboards and objects associated with the dashboard. A security profile consists of the access permissions and data restrictions that the system administrator sets for a user or group. 7. Exporting a Group Security Profile You can export a security profile for only one group at a time. The Save As window appears. Data Analyzer lists one page of users and displays the page numbers at the top. 5. Data Analyzer does not export access permissions for filtersets. it exports access permissions for objects under the Schema Directory. To export a user security profile: 1. or shared documents. click the page number. If there are a large number of users in the repository. Navigate to the directory where you want to save the file. If a user or group security profile you export does not have access permissions or data restrictions. 4. When Data Analyzer exports a security profile. Click Save. 6. Select a user whose security profile you want to export. 2. metrics. Click Export as XML.

Navigate to the directory where you want to save the file. 4. The Export Security Profile page displays a list of all the groups in the repository. 3. Click Administration > XML Export/Import > Export Security Profile. 7. Data Analyzer does not export the history of the schedule. 5. Select the group whose security profile you want to export. Data Analyzer lists one page of groups and displays the page numbers at the top. Click Save. The Save As window appears. 46 Chapter 6: Exporting Objects from the Repository . Click Export from Groups. Enter a name for the XML file and click Save. Click Save. Data Analyzer exports the security profile definition for the selected group. To view groups on other pages. Click Export as XML. 6. To export a schedule: 1. 6. Click Administration > XML Export/Import > Export Schedules. The File Download window appears. Select the schedule you want to export. 5. When you export a schedule. The Save As window appears. The File Download window appears. Data Analyzer exports the definitions of all selected schedules. Navigate to the directory where you want to save the file. Data Analyzer runs a report with an event-based schedule when a PowerCenter session completes. Click Export as XML. The Export Schedules page displays a list of the schedules in the repository. Exporting a Schedule You can export a time-based or event-based schedule to an XML file. 2. 4. Data Analyzer runs a report with a timebased schedule on a configured schedule. If there are a large number of groups in the repository.To export a group security profile: 1. click the page number. 3. You can click Names at the top of the list to select all schedules in the list. Enter a name for the XML file and click Save. 2.

Troubleshooting 47 . do not edit the file. The web browser cannot locate the DTD file Data Analyzer uses for exported objects. Error processing resource 'Principal<DTDVersion>. Use a text editor to open the XML file. I double-click the XML file and receive the following error: The system cannot locate the resource specified.dtd'.Troubleshooting After I export an object. Changes might invalidate the file. However. If you double-click the XML file. the operating system tries to open the file with a web browser.

48 Chapter 6: Exporting Objects from the Repository .

see “Localization” on page 7. 57 Importing a Security Profile. 56 Importing a Dashboard. 50 Importing a Time Dimension. For more information. 59 Importing a Schedule.CHAPTER 7 Importing Objects to the Repository This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview. both repositories must have the same language type and locale settings. 49 Importing a Schema. 53 Importing a Report. Data Analyzer imports objects based on the following constraints: ♦ 49 . or. the destination repository must be a superset of the source repository. 62 Overview You can import objects into the Data Analyzer repository from a valid XML file of exported repository objects. When you import a repository object that was exported from a different repository. You can import the following repository objects from XML files: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Schemas Time dimensions Reports Global variables Dashboards Security profiles Schedules Users Groups Roles You can import objects into the same repository or a different repository. 61 Troubleshooting. 54 Importing a Global Variable.

If you try to import an invalid XML file. A valid XML file can contain definitions of the following schema objects: ♦ Tables. Except for global variables. Ordinarily. You cannot overwrite global variables that already exist in the repository. Exporting and importing repository objects use considerable system resources. you can choose to overwrite the existing objects. Data Analyzer 8. Importing a Schema You can import schemas from an XML file. Make sure that you schedule exporting and importing tasks so that you do not disrupt Data Analyzer users. You must ensure that you do not modify an XML file of exported objects. you can limit access to the report for users who are not system administrators by clearing the Publish to Everyone option. if you import objects that already exist in the repository. all users in Data Analyzer have read and write access to the report. when you import a Data Analyzer 5. For example. you might not be able to use it to import objects into a Data Analyzer repository. if you are not sure of the validity of an XML file. Importing Objects from a Previous Version You can import objects from Data Analyzer 5.0 or later. you can validate it against the Data Analyzer DTD file when you start the import process.0 report using a custom attribute with groups. Data Analyzer grants you the same permissions to the object as the owner of the object.x upgrades the attribute to one with an advanced expression. However. you do not need to validate an XML file that you create by exporting from Data Analyzer. The schema tables associated with the exported metrics in the XML file. you can validate the XML file against the DTD provided by Data Analyzer. You can then change the access permissions to the report to restrict specific users or groups from accessing it. Data Analyzer system administrators can access all imported repository objects. users might experience slow response or timeout errors. XML Validation When you import objects.0 repositories or later. see “Importing Objects from a Previous Version” on page 50.♦ ♦ You can import objects from Data Analyzer 5. You might want to back up the target repository before you import repository objects into it. see the PowerCenter Administrator Guide. For more information about upgrading objects in the repository. If you publish an imported report to everyone. When you import objects from a previous version. Data Analyzer upgrades the objects to the current version. You can back up a Data Analyzer repository in the PowerCenter Administration Console. For more information. Data Analyzer stops the import process and displays the following message: Error occurred when trying to parse the XML file. The file might include the following tables: − − − Fact table associated with the metric Dimension tables associated with the fact table Aggregate tables associated with the dimension and fact tables 50 Chapter 7: Importing Objects to the Repository . For more information. If you modify the XML file. If you perform these tasks while users are logged in to Data Analyzer. see the PowerCenter Configuration Guide. Object Permissions When you import a repository object. When you import a report. You can also import repository objects using the ImportExport command line utility.

− − ♦ Snowflake dimensions associated with the dimension tables Template dimensions associated with the dimension tables or exported separately Schema joins. The drill paths associated with exported attributes. The file can include calculated metrics and base metrics. Attributes. The attributes in the fact and dimension tables associated with the exported metrics in the XML file. When you import a schema. Operational schemas. you must make sure that the fact table for the metric exists in the target repository. Imported Schema Table Description Property Name Last Modified Date Last Modified By Description Name of the fact or dimension tables associated with the metric to be imported. The Import Schemas page appears. schema joins. When you import an operational schema. the XML file contains different types of schema objects. Time keys. Data Analyzer imports the metrics and attributes in the hierarchical schema. The relationships between tables associated with the exported metrics in the XML file. Data Analyzer imports the following objects: − − − Tables in the operational schema Metrics and attributes for the operational schema tables Schema joins ♦ Hierarchical schemas. All metrics exported to the XML file. If you export the metric definition only. You can choose to overwrite objects in the repository. Click Open. It then displays a list of all the object definitions in the XML file that already exist in the repository. 2. Date when the table was last modified. metrics. If the XML file contains only the metric definition. 5. The time keys associated with exported tables. drill paths. User name of the Data Analyzer user who last modified the table. The lists of schema tables. Click Browse to select an XML file from which to import schemas. If you import a schema that contains time keys. When you export metrics with the associated schema tables and attributes. You can import a metric only if its associated fact table exists in the target repository or the definition of its associated fact table is also in the XML file. time keys. The name and location of the XML file display on the Import Schemas page. 3. Click Import XML. Click Administration > XML Export/Import > Import Schemas. select Validate XML against DTD. To validate the XML file against the DTD. and operational schemas display in separate sections. Data Analyzer displays a list of all the definitions contained in the XML file. To import a schema: 1. Drill paths. 4. Importing a Schema 51 . attributes. When you import a hierarchical schema. Table 7-1 shows the information that Data Analyzer displays for schema tables: Table 7-1. you must import or create a time dimension. see “Importing a Time Dimension” on page 53. The file can include the following relationships: − − Fact table joined to a dimension table Dimension table joined to a snowflake dimension ♦ ♦ ♦ ♦ ♦ Metrics. For more information. the XML file contains only a list of metric definitions.

User name of the person who last modified the metric. Can also be the name of a snowflake dimension table associated with a dimension table. Date when the drill path was last modified.ForeignKey = Table. Imported Schema Join Expression Property Table1 Name Description Name of the fact table that contains foreign keys joined to the primary keys in the dimension tables. User name of the person who last modified the attribute. Foreign key and primary key columns that join a fact and dimension table or a dimension table and a snowflake dimension in the following format: Table. Can also be the name of a dimension table that joins to a snowflake dimension.PrimaryKey Table2 Name Join Expression Table 7-3 shows the information that Data Analyzer displays for the metrics: Table 7-3. Imported Drill Paths Information Property Name Last Modified Date Last Modified By Paths Description Name of the drill path that includes attributes in the fact or dimension tables associated with the metric to be imported. Table 7-5 shows the information that Data Analyzer displays for the drill paths: Table 7-5. square brackets ([]) display in place of a fact table. Fact or dimension table that contains the attribute.Table 7-2 shows the information that Data Analyzer displays for the schema joins: Table 7-2. List of attributes in the drill path that are found in the fact or dimension tables associated with the metric to be imported. Imported Metrics Information Property Name Last Modified Date Last Modified By Analyzer Table Locations Description Name of the metric to be imported. User name of the person who last modified the drill path. Table 7-4 shows the information that Data Analyzer displays for the attributes: Table 7-4. Name of the dimension table that contains the primary key joined to the foreign keys in the fact table. 52 Chapter 7: Importing Objects to the Repository . Imported Attributes Information Property Name Last Modified Date Last Modified By Analyzer Table Locations Description Name of the attributes found in the fact or dimension tables associated with the metric to be imported. Date when the attribute was last modified. If the metric is a calculated metric. Date when the metric was last modified. Fact table that contains the metric.

Imported Hierarchical Schema Information Property Name Last Modified Date Last Modified By 6. Table 7-7 shows the information that Data Analyzer displays for the operational schemas: Table 7-7. To overwrite only specific schema objects. Click Apply. Data Analyzer imports the primary attribute. Description Name of the hierarchical schema to be imported. Data Analyzer imports the definitions of all selected schema objects. 2. To import a time dimension table: 1. The name and location of the XML file display on the Import Time Dimensions page. Imported Time Keys Information Property Name Description Name of the time key associated with the fact table. If you select to overwrite schema objects. select Overwrite All.and time-related attributes that describe the occurrence of metrics and establish the time granularity of the data in the fact table. To overwrite all the schema objects. User name of the person who last modified the hierarchical schema. a list of the duplicate objects appears. 4. 7. To overwrite the schema objects of a certain type. select the object. The Import Time Dimensions page appears. select Validate XML against DTD. To validate the XML file against the DTD.Table 7-6 shows the information that Data Analyzer displays for the time keys: Table 7-6. User name of the person who last modified the operational schema. confirm that you want to overwrite the objects. and calendar attribute of the time dimension table. Click Continue. Click Open. Importing a Time Dimension 53 . secondary attribute. If objects in the XML file are already defined in the repository. select Overwrite at the top of each section. Imported Operational Schemas Information Property Name Last Modified Date Last Modified By Description Name of the operational schema to be imported. Click Administration > XML Export/Import > Import Time Dimensions. Table 7-8 shows the information that Data Analyzer displays for the hierarchical schemas: Table 7-8. You can import a time dimension table from an XML file. Date when the operational schema was last modified. When you import a time dimension table. Date when the hierarchical schema was last modified. Click Browse to select an XML file from which to import time dimensions. 3. Importing a Time Dimension Time dimension tables contain date.

Data Analyzer imports all data for each component. Click Import XML. If you successfully import the time dimensions.5. Depending on the reports included in the file and the options selected when exporting the reports. 7. The user who imports the report becomes the owner of the gauge indicator. 8. Data Analyzer displays a message that you have successfully imported the time dimensions. a list of the duplicate objects appears. Click Continue. Imported public highlighting uses the state set for all users as the default highlighting state. If objects in the XML file are already defined in the repository. User name of the Data Analyzer user who last modified the report. the XML file might not contain all supported metadata. 6. Imported Time Dimension Information Property Name Last Modified Date Last Modified By Description Name of the time dimension table. with the following exceptions: ♦ ♦ ♦ 54 Chapter 7: Importing Objects to the Repository . Data Analyzer displays the time dimensions found in the XML file. Imported personal and public alerts use the state set for all report subscribers as the default alert state. Highlighting. Alerts. Table 7-9 shows the information that Data Analyzer displays for the time dimensions: Table 7-9. Importing a Report You can import reports from an XML file. If the gauge indicator is personal. Data Analyzer does not export any personal highlighting. it becomes personal to the user who imports the report. Click Continue. Select the objects you want to overwrite. Date when the time dimension table was last modified. Data Analyzer imports the following components of a report: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Report table Report chart Indicators Alerts Filters Filtersets Highlighting Calculations Custom attributes All reports in an analytic workflow Permissions Report links Schedules Gauge indicators. Imported gauge indicators do not keep their original owner. When available. Data Analyzer imports the definitions of all selected time dimensions.

If a report of the same name already exists in the same folder. Thus. the following error appears: Result set is null. Click Administration > XML Export/Import > Import Reports. To validate the XML file against the DTD. Data Analyzer does not import report data for cached reports. and global variables used in the report are defined in the target repository. it imports reports from the public folder to the public folder. you must import or recreate the objects before you run the report. When you import a report exported from a personal folder. 3. 2. Click Browse to select an XML file from which to import reports. The Import Reports page appears. For example. If during the export process. you first must run the report. For example. you can overwrite the existing report. Data Analyzer creates a new folder of that name for the report. You can import cached and on-demand reports. You can also edit the report and save it before you view it to make sure that Data Analyzer runs the report before displaying the results. Data Analyzer does not import analytic workflows containing the same workflow report names. Running reports in the background can be a long process.When you import a report. Data Analyzer creates a public folder called Personal Reports with the import date. Importing Reports from Public or Personal Folders You can import reports exported from any folder in the repository. such as Personal Reports (Imported 8/10/04). ensure that all imported analytic workflows have unique report names prior to export. attributes. select Validate XML against DTD. Click Open. Data Analyzer creates a new folder within the public folder called Personal Reports with the date of import and creates a subfolder named for the owner of the personal folder. you are the owner of the new public folder. and copies the imported report into a subfolder called Mozart. the XML file contains all the subreports. If you try to view an imported cached report immediately after you import it. When possible. If you import a report that uses objects not defined in the target repository. Importing a Report 55 . and the data may not be available immediately. Click Import XML. 4. To view the data for the report. the XML file contains all workflow reports. Data Analyzer imports reports to the same folder in the target repository. If you import a report and its corresponding analytic workflow. You can choose to overwrite the subreports or composite report if they are already in the repository. if you import a report exported from a personal folder called Mozart. 5. When Data Analyzer imports a report to a repository that does not have the same folder as the originating repository. Steps for Importing a Report To import a report: 1. then Data Analyzer also imports the schedule stored in the cached report. make sure all the metrics. You can run imported cached reports in the background immediately after you import them. When importing multiple workflows. Data Analyzer displays the reports found in the XML file. If you choose to overwrite the report. Data Analyzer also overwrites the workflow reports. To ensure security for the reports from the personal folders. you chose to export schedules associated with a report. If you import a composite report. The name and location of the XML file display on the Import Reports page.

Data Analyzer displays a list of the undefined objects. To immediately update the data for all the cached reports in the list. Data Analyzer imports only the global variables that are not in the target repository. Click Administration > XML Export/Import > Import Global Variables. select Publish to Everyone. Data Analyzer displays the global variables found in the XML file. 56 Chapter 7: Importing Objects to the Repository . The name and location of the XML file display on the Import Global Variables page. To validate the XML file against the DTD. you might not be able to run it successfully. Create the required objects in the target repository before attempting to import the report again. To allow all users to have access to the reports. Date when the report was last modified. For more information about attaching the imported cached reports to a schedule immediately. If you continue the import process. If the XML file contains global variables already in the repository. If attributes or metrics associated with the report are not defined in the repository. User name of the Data Analyzer user who last modified the report. Click Continue. To cancel the import process. Data Analyzer lists any folders created for the reports. Data Analyzer runs the cached reports in the background. select Overwrite at the top of the list. Click Open. 7. 2. Click Import XML. 8.Table 7-10 shows the properties that Data Analyzer displays for the reports: Table 7-10. Location of the report in the Public Folders or Personal Folder. Data Analyzer displays a message that you have successfully imported them. Click Browse to select an XML file from which to import global variables. Importing a Global Variable You can import global variables that are not defined in the target repository. If reports in the XML file are already defined in the repository. 3. you can cancel the process. Data Analyzer imports the definitions of all selected reports. select Validate XML against DTD. Description Name of the reports found in the XML file. select Run Cached Reports after Import. If you import cached reports. select Overwrite next to the report name. The Import Global Variables page appears. a list of the duplicate reports appears. it displays a message that you need to assign the cached reports to a schedule in the target repository. Click Continue. Imported Report Properties Property Name Last Modified Date Last Modified By Path 6. When necessary. To overwrite all reports. If you import the report. To overwrite any of the reports. 4. 5. see “Attaching Imported Cached Reports to a Time-Based Schedule” on page 26 and “Attaching Imported Cached Reports to an Event-Based Schedule” on page 37. If you successfully import the reports. click Cancel. After you import the reports. To import a global variable: 1.

If you continue the import process. Description Name of the global variable found in the XML file. Data Analyzer does not import global variables whose names exist in the repository. Data Analyzer creates a new folder of that name for the dashboard. and indicators. ♦ ♦ ♦ When you import a dashboard. Data Analyzer imports the dashboards to the Public Folders > Dashboards folder. If an object exists in the repository. Dashboards exported from an earlier version of Data Analyzer. Data Analyzer imports the dashboards to a new Public Folders > Personal Dashboards (Imported MMDDYY) > Owner folder. Data Analyzer imports all indicators for the originating report and workflow reports in a workflow. Data Analyzer provides an option to overwrite the object. If the XML file includes global variables already in the repository. However. Importing a Dashboard 57 . If the Dashboards folder already exists at the time of import. click Continue. Data Analyzer stores the imported dashboard in the following manner: ♦ Dashboards exported from a public folder. shared documents. Value of the global variable. To continue the import process. Click Continue. Data Analyzer imports the following objects associated with the dashboard: ♦ ♦ ♦ ♦ ♦ ♦ Reports Indicators Shared documents Dashboard filters Discussion comments Feedback Access permissions Attributes and metrics in the report Real-time objects Data Analyzer does not import the following objects associated with the dashboard: ♦ ♦ ♦ Dashboards are associated with the folder hierarchy. indicators for workflow reports do not display on the dashboard after you import it. Data Analyzer displays a warning. You must add those indicators to the dashboard manually. Data Analyzer imports a personal dashboard to the Public Folders folder. When you import a dashboard from an XML file.Table 7-11 shows the information that Data Analyzer displays for the global variables: Table 7-11. Dashboards exported from a personal folder. Personal dashboard. then Data Analyzer creates a new Public Folders > Dashboards_n folder to store the dashboards (for example. Data Analyzer imports only the variables that are not in the repository. Importing a Dashboard Dashboards display links to reports. Dashboards_1 or Dashboards_2). When Data Analyzer imports a dashboard to a repository that does not have the same folder as the originating repository. even if the values are different. When you import a dashboard. Imported Global Variable Description Property Name Value 6. Data Analyzer imports the dashboards to the corresponding public folder in the target repository.

reports. 6. and shared documents already defined in the repository. Click Continue. If the attributes or metrics in a report associated with the dashboard do not exist. 8. Table 7-12 shows the information that Data Analyzer displays for the dashboards: Table 7-12. select Overwrite next to the item name. reports. Click Browse to select an XML file from which to import dashboards. click Cancel. The name and location of the XML file display on the Import Dashboards page. Click Open. select Overwrite at the top of the list. 2. select Validate XML against DTD. To continue the import process. Data Analyzer displays the list of dashboards found in the XML file. Click Apply. If the attributes or metrics in a report associated with the dashboard do not exist. The Import Dashboards page appears. the report does not display on the imported dashboard. Click Administration > XML Export/Import > Import Dashboards.When you import a dashboard. report. or shared documents. 4. Click Import XML. 5. User name of the Data Analyzer user who last modified the dashboard. You must manually subscribe to imported dashboards to display them in the Subscription menu. Data Analyzer imports the definitions of all selected dashboards and the objects associated with the dashboard. 58 Chapter 7: Importing Objects to the Repository . Data Analyzer displays a list of the metrics and attributes in the reports associated with the dashboard that are not in the repository. the report does not display on the imported dashboard. Imported Dashboard Information Property Name Last Modified Date Last Modified By Description Name of the dashboard found in the XML file. 3. Data Analyzer does not automatically display imported dashboards in your subscription list on the View tab. click Apply. To cancel the import process. Date when the dashboard was last modified. To import a dashboard: 1. To validate the XML file against the DTD. Data Analyzer does not import the attributes and metrics in the reports associated with the dashboard. make sure all the metrics and attributes used in reports associated with the dashboard are defined in the target repository. 7. To overwrite all dashboards. or shared document. Data Analyzer displays a list of the dashboards. To overwrite a dashboard.

4. To validate the XML file against the DTD. Click Overwrite to replace existing security profiles with the imported security profile. including folders. Click Import XML. 5. When you overwrite a security profile. select Import To All. You can assign the same security profile to more than one user or group. Or. Click Import to Users. If you append the profile. The Sales group has an existing Sales fact table data restriction: Region Name show only ‘Europe’. you can either overwrite the current security profile or add to it. When a user or group has a data restriction and the imported security profile has a data restriction for the same fact table or schema and associated attribute. Data Analyzer keeps a security profile for each user or group in the repository. Select the users you want to associate with the security profile. the Sales group restriction changes to show only data related to the United States. Data Analyzer joins the restrictions using the OR operator. 3. click Append to add the imported security profile to existing security profiles. Data Analyzer appends new data restrictions to the old restrictions but overwrites old access permissions with the new access permissions. To associate the security profile with all users in the repository. Click Administration > XML Export/Import > Import Security Profiles. The Import Security Profiles window displays the access permissions and data restrictions for the security profile. Click Continue. The Import Security Profiles page appears. Importing a Security Profile 59 . To import a user security profile: 1. Data Analyzer removes the old restrictions associated with the user or group. the Sales group data restriction changes to the following restriction: Region Name show only ‘United States’ OR Region Name show only ‘Europe’. When you import a security profile and associate it with a user or group. Data Analyzer assigns the user or group only the data restrictions and access permissions found in the new security profile. select Validate XML against DTD. attributes. you import a security profile with the following data restriction for the Sales fact table: Region Name show only ‘United States’. Click Browse to select an XML file from which to import a security profile. you must first select the user or group to which you want to assign the security profile. 8.Importing a Security Profile A security profile consists of data restrictions and access permissions for objects in the Schema Directory. and metrics. select the check box under Users at the top of the list. Importing a User Security Profile You can import a user security profile and associate it with one or more users. When you import a security profile from an XML file. Click Open. 9. When you append a security profile. 7. For example. The name and location of the XML file display on the Import Security Profiles page. To associate the security profiles with all displayed users. The Import Security Profile page displays all users in the repository. 2. If you overwrite existing security profiles. 6.

Type Table 7-14 shows the information that Data Analyzer displays for the data restrictions: Table 7-14. To import a group security profile: 1. Click Continue. Imported Security Profile: Restricted Objects Property Object Name Description Indicates the Schema Directory path of the restricted schema object if the restricted object is a folder. Click Browse to select an XML file from which to import a security profile. Click Append to add the imported security profile to existing security profiles. or metric. 60 Chapter 7: Importing Objects to the Repository . Description Name of the restricted table found in the security profile. It imports access permissions and data restrictions only for objects defined in the repository. 9. Click Continue. To continue the import process. 5. Indicates the fact table and metric name if the object is a metric. Click Import to Groups. 11. select the check box under Groups at the top of the list. To associate the security profile with all groups in the repository. Data Analyzer imports the security profile and associates it with all selected users. The Import Security Profile page displays all groups in the repository. 3. 8. To cancel the import process. Indicates the fact or dimension table and attribute name if the object is an attribute. To associate the security profiles with all displayed groups. 4. Data Analyzer displays a list of the objects in the security profile that are not in the repository.Table 7-13 shows the information that Data Analyzer displays for the restricted objects: Table 7-13. attribute. Click Import XML. 7. To validate the XML file against the DTD. Select the groups you want to associate with the security profile. 6. Indicates whether the schema object is a folder. Click Open. 2. The name and location of the XML file display on the Import Security Profile page. The Import Security Profile page appears. Click Administration > XML Export/Import > Import Security Profile. Imported Security Profile: Data Restrictions Property Schema Table Name Security Condition 10. The list of access permissions and data restrictions that make up the security profile appears. Click Continue. 10. Click Overwrite to replace existing security profiles with the imported security profile. click Continue. Importing a Group Security Profile You can import a group security profile and associate it with one or more groups. click Cancel. select Import To All. select Validate XML against DTD. Description of the data access restrictions for the table.

User name of the person who last modified the schedule. Importing a Schedule You can import a time-based or event-based schedule from an XML file. To validate the XML file against the DTD. click Continue. you do not import the task history or schedule history. 11. Data Analyzer imports the security profile and associates it with all selected groups. The name and location of the XML file display on the Import Schedules page. 6. Importing a Schedule 61 . The list of objects found in the XML file appears. To overwrite all schedules. When you import a schedule from an XML file. You can then attach reports to the imported schedule. click Cancel. Data Analyzer imports the schedules. 3. If the schedules in the XML file are already defined in the repository. Click Continue. To import a schedule: 1. 4. Click Continue. The Import Schedules page appears. When you import a schedule. Data Analyzer does not attach the schedule to any reports. Click Import XML. click the Overwrite check box next to the schedule. To cancel the import process. Imported Schedule Information Property Name Last Modified Date Last Modified By Description Name of the schedule found in the XML file. 5. To overwrite a schedule. a list of the duplicate schedules appears. Click Open. click the Overwrite check box at the top of the list. To continue the import process. Click Browse to select an XML file from which to import a schedule. Date when the schedule was last modified. select Validate XML against DTD. 2.Data Analyzer displays a list of the objects in the security profile that are not in the repository. 7. Table 7-15 shows the information that Data Analyzer displays for the schedules found in the XML file: Table 7-15. It imports access permissions and data restrictions only for objects defined in the repository. Click Administration > XML Export/Import > Import Schedules.

Data Analyzer generates different errors. run the following file extracted from the connectjdbc. You might need to contact your database system administrator to change some of these settings. For more information about editing the DataAnalyzer. On the Product Downloads page. When I import large XML files. 3.jar. You can now run large import processes without timing out.ssp To increase the value of the DynamicSections property: 1. The default value of the DynamicSections connection property is 200. If you use this driver to connect to a DB2 8. you might want to modify the following parameters: ♦ ♦ ♦ DynamicSections value of the JDBC driver Page size of the temporary table space Heap size for the application Increasing the DynamicSections Value Data Analyzer might display the following message when you import large XML files: javax.timeout. The error occurs when the default value of the DynamicSections property of the JDBC driver is too small to handle large XML imports. You must increase the default value of DynamicSections connection property to at least 500. Enter the following license key and click Add: 62 Chapter 7: Importing Objects to the Repository .jar file: Windows: Installer. click the DataDirect Connect for JDBC Any Java Platform link and complete the registration information to download the file. you can change the default transaction time out value. you must restart the application server. If you are importing large amounts of data from XML and the transaction time is not enough.sh 4.transaction. Is there a way to raise the transaction time out period? The default transaction time out for Data Analyzer is 3600 seconds (1 hour). Follow the instructions in the DataDirect Connect for JDBC Installation Guide. edit the value of the import. Please recreate your package with a larger dynamicSections value.ejb.com/download/index. Data Analyzer might display error messages when you import large XML files. I have an IBM DB2 8.seconds property in the DataAnalyzer.properties file. You can modify the settings of the application server.properties file.jar file in a temporary directory and install the DataDirect Connect for JDBC utility. see “Configuration Files” on page 129.Troubleshooting When I import my schemas into Data Analyzer. Extract the contents of the connectjdbc. or the JDBC driver to solve the problem.EJBException: nested exception is: Exception: SQL Exception: [informatica][DB2 JDBC Driver]No more available statements. How can I import large XML files? The Data Analyzer installer installs a JDBC driver for IBM DB2 8. The name of the download file is connectjdbc. On the command line.bat UNIX: Installer. Depending on the error that Data Analyzer generates. Download the utility from the Product Downloads page of DataDirect Technologies web site: http://www. Use the DataDirect Connect for JDBC utility to increase the default value of the DynamicSections connection property and recreate the JDBC driver package. 2. the database.x repository database. To change the default transaction time out for Data Analyzer.x repository. After you change this value.x.datadirect. I run out of time.

Restart the application server. Click Connection > Connect to DB. If you continue getting the same error message when you import large XML files. 7. increase the value of the application heap size configuration parameter (APPLHEAPSZ) to 512. log out of Data Analyzer and stop the application server. see the IBM DB2 documentation. Modifying the Page Size of the Temporary Table Space Data Analyzer might display the following message when you import large XML files: SQL1585N A temporary table space with sufficient page size does not exist This problem occurs when the row length or number of columns of the system temporary table exceeds the limit of the largest temporary table space in the database. create a new system temporary table space with the page size of 32KB. In the Database field. The installation program for the DataDirect Connect for JDBC utility creates the testforjdbc folder in the directory where you extracted the connectjdbc. 9. enter the following: jdbc:datadirect:db2://<ServerName>:<PortNumber>. To resolve the error. For more information. Troubleshooting 63 . databaseName=<DatabaseName>. 6. In the testforjdbc folder.eval 5. Increasing Heap Size for the Application Data Analyzer might display the following message when you import large XML files: [informatica][DB2 JDBC Driver][DB2]Virtual storage or database resource is not available ErrorCode=-954 SQLState=57011 This problem occurs when there is not enough storage available in the database application heap to process the import request. Click Connect. On the Test for JDBC Tool window. see the IBM DB2 documentation. enter the user name and password you use to connect to the repository database from Data Analyzer.sh 8. 12. On the repository database.jar file. PortNumber is the port number of the database. 10. For more information. 13. ReplacePackage=TRUE. 11. you can run the Test for JDBC Tool again and increase the value of DynamicSections to 750 or 1000.DynamicSections=500 ServerName is the name of the machine hosting the repository database.bat UNIX: testforjdbc. Click Finish to complete the installation. In the User Name and Password fields.CreateDefaultPackage=TRUE. click Press Here to Continue. DatabaseName is the name of the repository database. Click Next twice and then click Install. To resolve the problem. run the Test for JDBC Tool: Windows: testforjdbc. Restart the application server. and then close the window.

64 Chapter 7: Importing Objects to the Repository .

Data Analyzer does not store user passwords in the Data Analyzer repository. 70 Overview The Import Export utility lets you import and export Data Analyzer repository objects from the command line. You can also use the Data Analyzer Administration tab to import or export all objects of a specified type. For example. You must run the utility multiple times to import or export different types of objects. use the Data Analyzer Administration tab. 69 Troubleshooting. To import or export individual objects. 65 . You can use the Import Export utility to import objects from Data Analyzer 5. 66 Error Messages.CHAPTER 8 Using the Import Export Utility This chapter includes the following topics: ♦ ♦ ♦ ♦ Overview. You cannot use the utility to import or export other individual objects. 65 Running the Import Export Utility. groups. For example. Use the utility to import or export the security profile of an individual user or group. When you run the Import Export utility. you can use the utility to quickly migrate Data Analyzer repository objects from a development repository into a production repository. Data Analyzer authenticates the passwords directly in the LDAP directory. For example. When you use the Import Export utility.0 repositories or later. you cannot use the Import Export utility to import users. If Data Analyzer is installed with the LDAP authentication method. You can also use the utility to archive your repository without using a browser. you can run the utility to import all reports from an XML file or export all dashboards to an XML file. the same rules as those about import or export from the Data Analyzer Administration tab apply. With the LDAP authentication method. Data Analyzer imports or exports all objects of a specified type. or roles. with the Import Export utility or the Data Analyzer Administration tab. Use the Import Export utility to migrate repository objects from one repository to another. For example. you cannot use the utility to export a specific user or report to an XML file. you can import only those global variables that do not already exist in the repository.

Running the Import Export Utility
Before you run the Import Export utility to import or export repository objects, you must meet the following requirements:
♦ ♦

To run the utility, you must have the System Administrator role or the Export/Import XML Files privilege. To import or export users, groups, or roles, you must also have the Manage User Access privilege. Data Analyzer must be running.

You can import Data Analyzer objects from XML files that were created when you exported repository objects from Data Analyzer. You can use files exported from Data Analyzer 5.0 or later. The default transaction time out for Data Analyzer is 3,600 seconds (1 hour). If you are importing large amounts of data from XML files and the transaction time is not enough, you can change the default transaction time out value. To change the default transaction time out for Data Analyzer, edit the value of the import.transaction.timeout.seconds property in DataAnalyzer.properties. After you change this value, you must restart the application server. When you run the Import Export utility, you specify options and arguments to import or export different types of objects. Specify an option by entering a hyphen (-) followed by a letter. The first word after the option letter is the argument. To specify the options and arguments, use the following rules:
♦ ♦ ♦ ♦

Specify the options in any order. Utility name, options, and argument names are case sensitive. If the option requires an argument, the argument must follow the option letter. If any argument contains more than one word, enclose the argument in double quotes.

To run the utility on Windows, open a command line window. On UNIX, run the utility as a shell command.
Note: Back up the target repository before you import repository objects into it. You can back up a Data

Analyzer repository with the Repository Backup utility.
To run the Import Export utility: 1.

Go to the Data Analyzer utilities directory. The default directory is <PCAEInstallationDirectory>/DataAnalyzer/import-exportutil/.

2.

Run the utility with the following format: Windows:
ImportExport [-option_1] argument_1 [-option_2] argument_2 ...

UNIX:
ImportExport.sh [-option_1] argument_1 [-option_2] argument_2 ...

Table 8-1 lists the options and arguments you can specify:
Table 8-1. Options and Arguments for the Import Export Utility
Option -i Argument repository object type Description Import a repository object type. For more information about repository object types, see Table 8-2 on page 68. Use the -i or -e option, but not both. Export a repository object type. For more information about repository object types, see Table 8-2 on page 68. Use the -i or -e option, but not both.

-e

repository object type

66

Chapter 8: Using the Import Export Utility

Table 8-1. Options and Arguments for the Import Export Utility
Option -w Argument No argument Description Import only. Instructs the Import Export utility to overwrite existing repository objects of the same name. If you do not specify this option and if a repository object with the same name already exists, the utility exits without completing the operation. If you do not use a hyphen when importing a security profile, the security profile being imported is appended to the existing security profile of the user or group. If you use this option when exporting repository objects, the utility displays an error message. Name of the XML file to import from or export to. The XML file must follow the naming conventions for the operating system where you run the utility. You can specify a path for the XML file. If you specify a path for the XML file: - When you import a repository object type, the Import Export utility looks for the XML file in the path you specify. - When you export an object type, the utility saves the XML file in the path you specify. For example, to have the utility save the file in the c:/PA directory, enter the following command:
ImportExport -e user -f c:/PA/Users.xml -u admin -p admin -l http://my.server.com:7001/ias

-f

XML file name

If you do not specify a path for the XML file: - When you import a repository object type, the Import Export utility looks for the XML file in the directory where you run the utility. - When you export an object type, the utility saves the XML file in the directory where you run the utility. For example, when you enter the following command, the utility places Users.xml in the directory where you run the utility:
ImportExport -e user -f Users.xml -u admin -p admin -l http://my.server.com:7001/ias

-u -p -l

user name password url

Data Analyzer user name. Password for the Data Analyzer user name. URL for accessing Data Analyzer. Contact the system administrator for the URL. The Data Analyzer URL has the following format:
http://host_name:port_number/ ReportingServiceName

ReportingServiceName is the name of the Reporting Service that runs the Data Analyzer instance. For example, PowerCenter runs on a machine with hostname fish.ocean.com and has a Reporting Service named IASReports with port number 18080. Use the following URL for Data Analyzer:
http://fish.ocean.com:18080/IASReports

-h -n

No argument user name or group name

Displays a list of all options and their descriptions, and a list of valid repository objects. Use to import or export the security profile of a user or group. For more information, see Table 8-2 on page 68.

Running the Import Export Utility

67

Table 8-2 lists the repository object types you can import or export using the Import Export utility and an example for each. Enter the repository object type as listed below:
Table 8-2. Valid Repository Object Types
Repository Object Type schema Description Schemas Example To import schemas from the PASchemas.xml file into the repository, use the following command:
ImportExport -i schema -f c:\PASchemas.xml -u jdoe -p doe -l http://localhost:7001/ias

timedim

Time dimension tables

To import time dimension tables from the TD.xml file into the repository, use the following command:
ImportExport -i timedim -f TD.xml -u jdoe -p doe -l http://localhost:7001/ias

report

Reports

To import reports from the Reports.xml file into the repository, use the following command:
ImportExport -i report -f c:\Reports.xml -u jdoe -p doe -l http://localhost:7001/ias

variable

Global variables. You can import global variables that do not already exist in the repository. Dashboards

To export global variables to the GV.xml file, use the following command:
ImportExport -e variable -f c:\xml\GV.xml -u jdoe -p doe -l http://server:7001/ias

dashboard

To export dashboards to the Dash.xml file, use the following command:
ImportExport -e dashboard -f c:\Dash.xml -u jdoe -p doe -l http://localhost:7001/ias

usersecurity <security profile option>

Security profile of a user. You must specify the following security profile option: -n <user name> Security profile of a group. You must specify the following security profile option: -n <group name> Schedules

To export the security profile of user jdoe to the JDsecurity.xml file, use the following command:
ImportExport -e usersecurity -n jdoe -f JDsecurity.xml -u admin -p admin -l http://localhost:7001/ias

groupsecurity <security profile option>

To export the security profile of group Managers to the Profiles.xml file, use the following command:
ImportExport -e groupsecurity -n Managers -f Profiles.xml -u admin -p admin -l http://localhost:7001/ias

schedule

To export all schedules to the Schedules.xml file, use the following command:
ImportExport -e schedule -f c:\Schedules.xml -u jdoe -p doe -l http://localhost:7001/ias

user

Users

To export all users to the Users.xml file, use the following command:
ImportExport -e user -f c:\Users.xml -u jdoe -p doe -l http://localhost:7001/ias

group

Groups

To import groups from the Groups.xml file into the repository, use the following command:
ImportExport -i group -f c:\Groups.xml -u jdoe -p doe -l http://localhost:7001/ias

role

Roles

To import roles from the Roles.xml file into the repository, use the following command:
ImportExport -i role -f c:\Roles.xml -u jdoe -p doe -l http://localhost:7001/ias

The Import Export utility runs according to the specified options. If the utility successfully completes the requested operation, a message indicates that the process is successful. If the utility fails to complete the requested operation, an error message displays.

68

Chapter 8: Using the Import Export Utility

groups. Cause: Action: The user does not exist in Data Analyzer or password is incorrect. Unknown option. make sure there is enough hard disk space. Cause: Action: The XML file specified for the import (-i) option does not contain the correct object type. Cause: Action: The XML file to be imported does not exist or does not contain valid XML data or the utility cannot access the file. Check the validity and case sensitivity of the option letters. Cause: Action: Utility failed to run for unknown reasons. Use the correct object type or a different XML file. The export file cannot be written.Error Messages If the Import Export utility fails to complete the requested operation. The Import Export utility can display the following error messages: Unknown error. Incorrect number of command-line options. Cause: Action: The directory where you want to place the XML file is read only or has run out of hard disk space. Error Messages 69 . Cause: Action: You entered an incorrect option letter. The import file contains a different repository object type than the repository object type given for the option -i. with the specified name. you entered -x or -E to export a file. and a list of valid repository objects. it displays an error message. Or. Check the syntax and spelling. Cause: Action: The user does not have the Export/Import XML Files privilege or the Manage User Access privilege to import or export users. Invalid username or password. If the requested operation fails because a required option or argument is missing or not specified correctly. Check the XML file name. Illegal option value. Cause: Action: You entered an incorrect argument for an option letter. Assign the appropriate privileges to the user. The user does not have privileges to import/export. Cause: Action: You omitted an option or included more options than needed. The import file does not exist or cannot be read. Check the spelling of the option values you entered. The error message indicates why the requested operation failed. Assign write permission to the user for the directory where you want to place the XML file. Check that a valid XML file. exists in the specified directory. Contact the system administrator or Informatica Global Customer Support. Check that the user exists in Data Analyzer or the password is correct. or roles. For example. the Import Export utility also displays a list of all options and their descriptions.

and then run the utility. Contact the Data Analyzer system administrator. The root cause is: <error message>. An export file with the provided filename already exists. Check that Data Analyzer is running and try to run the utility again. Troubleshooting Importing a Large Number of Reports If you use the Import Export utility to import a large number of reports (import file size of 16MB or more). increase the value for the -mx option in the script file that starts the utility. groups. the Java process for the Import Export utility might run out of memory and the utility might display an exception message. Cause: Action: There is no data in the XML file. Use a valid XML file. 70 Chapter 8: Using the Import Export Utility . The configured security realm does not support the import of users. the Import Export utility displays this error message. increase the memory allocation for the process. Cause: Action: User name or group name that you typed for importing or exporting a security profile does not exist. If the Java process for the Import Export utility runs out of memory. Cause: You cannot import global variables if they already exist in the repository. Cause: Action: Data Analyzer is installed with the LDAP authentication method. Check the spelling of the user name or group name. If error still occurs. The action depends on the root cause. Cause: Action: An XML file of the same name already exists in the specified path. Global variables cannot be overwritten. Run the utility again. Cause: Action: See the root cause message. To increase the memory allocation for the Java process. Cause: Action: Data Analyzer session has timed out. If the XML file includes global variables already in the repository. or roles. Note: Back up the script file before you modify it. contact Informatica Global Customer Support. If you want to import global variables already in the repository. Action: Import file is empty. groups and roles. Check that the URL is correct and try to run the utility again. You cannot use the Import Export utility to import users. first delete them from Data Analyzer.A communication error has occurred with Data Analyzer. Delete the XML file before you enter the command. The user or group does not exist. The Data Analyzer session is invalid.

make sure that the URL you provide with the -l option starts with https:// and uses the correct port for the SSL connection. If the utility still displays an exception.ssl. Troubleshooting 71 . To specify the location of the trusted CAs: 1.sh 3. you do not need to specify the location of the trusted CA keystore when you run the Import Export utility. Using SSL with the Import Export Utility To use SSL. Locate the -mx option in the Java command: java -ms128m -mx256m -jar repositoryImportExport. such as Verisign.net.trustStore= If Data Analyzer uses a certificate signed by a CA defined in the default cacerts file.bat UNIX: ImportExport. Open the script file with a text editor: Windows: ImportExport. The default directory is <PCAEInstallationDirectory>/DataAnalyzer/import-exportutil/. Note: Back up the Import Export script file before you modify it. Data Analyzer needs a certificate that must be signed by a trusted certificate authority (CA). Save and close the Import Export utility file.ssl. By default. add the following parameter to the Import Export utility script: -Djavax. the trusted CAs are defined in the cacerts keystore file in the JAVA_HOME/jre/lib/security/ directory. Locate the Import Export utility script file in the Data Analyzer utilities directory. Open the script file with a text editor: Windows: ImportExport. Save and close the Import Export utility script file.To increase the memory allocation: 1.jar $* 4. If Data Analyzer uses a certificate signed by a CA not defined in the default cacerts file or if you have created your own trusted CA keystore.sh 3.trustStore=<TrustedCAKeystore> -jar repositoryImportExport. increase the value to 1024. Increase the value for the -mx option from 256 to a higher number depending on the size of the import file. Add the trusted CA parameter to the Java command that starts the ImportExport utility: java -ms128m -mx256m -Djavax. 5.jar TrustedCAKeystore is the keystore for the trusted CAs. Tip: Increase the value to 512. To specify the location of the trusted CAs. Locate the Import Export utility script in the Data Analyzer utilities directory: <PCAEInstallationDirectory>/DataAnalyzer/import-exportutil 2.bat UNIX: ImportExport. you must provide the location of the trusted keystore when you run the Import Export utility.net. When you run the Import Export utility. 2. 4.

72 Chapter 8: Using the Import Export Utility .

Determine whether scroll bars appear in report tables. and phone number of the Data Analyzer system administrator. LDAP settings. 74 Managing Logs. and logos of Data Analyzer to match those of your organization. images. System information. Register LDAP servers to enable users to access LDAP directory lists from Data Analyzer. 84 Viewing System Information. 85 Configuring Report Table Scroll Bars. Delivery settings. 90 Configuring Display Settings for Groups and Users. Log files. 73 Managing Color Schemes and Logos. Query governing. 83 Specifying Contact Information. 88 Configuring Departments and Categories. Contact information. Report settings. 81 Managing Delivery Settings. Define upper limits on query time. images. 84 Setting Rules for Queries. email address. 88 Configuring Report Headers and Footers. Modify the color schemes. View the configuration information of the machine hosting Data Analyzer. and receive alerts. Register an outbound mail server to allow users to email reports and shared documents. ♦ ♦ ♦ 73 . View Data Analyzer log files for information on user and system activity. and logos. 91 Overview You can configure the following administrative settings: ♦ ♦ ♦ ♦ ♦ Color schemes. Users might find the administrator contact information useful in the event of a system problem. report processing time. You can also configure alert delivery devices. and number of table rows displayed. 78 Managing LDAP Settings. Provide the name.CHAPTER 9 Managing System Settings This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Overview.

The color schemes and image files used in Data Analyzer are stored in the EAR directory. Enter the name of the logo image file you want to use. For the Informatica color scheme. Data Analyzer references the image and logo files in the Data Analyzer images directory on the web server associated with the application server. You can edit existing color schemes or create new color schemes. 2. Use any HTML hexadecimal color code to define colors. Metadata configuration. Create the headers and footers printed in Data Analyzer reports. the Informatica color scheme is the default color scheme for all users and groups in Data Analyzer. You can modify or add color schemes and images in the EAR directory to customize the Data Analyzer color schemes and images for the organization. For the Betton Books color scheme. Display Settings. You can also assign users and groups to specific color schemes. The EAR directory containing images for this color scheme is in the following location: /custom/images/standard This is the default image directory for Data Analyzer. ♦ Managing Color Schemes and Logos A color scheme defines the look and feel of Data Analyzer. Enter the name of the login page image file that you want to use. leave the Images Directory field blank. Using a Predefined Color Scheme Data Analyzer provides the following predefined color schemes that you can use or modify: ♦ Informatica color scheme. you can search for these objects by department or category on the Find tab. use green for the Images Directory field. using your own images and colors. 74 Chapter 9: Managing System Settings . Alternative predefined color scheme. ♦ Betton Books color scheme. 3. Logo Image URL. This is the default Data Analyzer color scheme. You can associate repository objects with a department or category to help you organize the objects. Edit the predefined color scheme and change the file name of the Logo Image URL field or the Login Page Image URL to the name of your image file. Create department and category names for your organization. Control display settings for users and groups.♦ ♦ Report header and footer. Predefined color scheme folder name. Enter the following information in the predefined color scheme settings: ♦ Images Directory. Login Page Image URL. ♦ ♦ All file names are case sensitive. When you associate repository objects with a department or category. You can set a default color scheme for all users and groups. Copy the logo or login image file to the predefined images folder. By default. The EAR directory containing images for the Betton Books color scheme is in the following location: /custom/images/standard/color/green Adding a Logo to a Predefined Color Scheme To use a predefined color scheme with your own logo or login page image. complete the following steps: 1.

3.com. If you specify a URL. Name of a logo file image in the color scheme directory or the URL to a logo image on a web server.com:7001/CompanyLogo. Enter hexadecimal color codes to represent the colors you want to use. Optionally. Section sub-heading such as the container sub-heading on the View tab. use the forward slash (/) as a separator. see “HTML Hexadecimal Color Codes” on page 121. Name of the login page image file in the color scheme directory or the URL to a login image on a web server. The Color Schemes and Logos page displays the list of available color schemes. To edit the settings of a color scheme. Data Analyzer uses all the colors and images of the selected predefined color scheme with your logo or login page image. Page header of Data Analyzer. Table 9-1 shows the display items you can modify in the Color Scheme page: Table 9-1. Section heading such as the container heading on the View tab. The Color Scheme page displays the settings of the color scheme. Click Administration > System Management > Color Schemes and Logos.You can also enter a URL for the logo and login image files.PaintersInc. For example. To display the login page properly. Name of a background image file in the color scheme directory or the URL to a background image on a web server. Managing Color Schemes and Logos 75 . the width of your login page image must be approximately 1600 pixels. Display Items in the Color Scheme Page Display Item Background Page Header Primary Secondary Heading Sub-Heading Description Background color of Data Analyzer. Background Image URL. and logo image files.PaintersInc. The height of your login page image must be approximately 240 pixels. Editing a Predefined Color Scheme You can edit the colors and image directories for predefined color schemes and preview the changes. Login Page Image URL. Logo Image URL. If you specify a URL. All file names are case sensitive. or the width of your monitor setting. you might lose your changes when you upgrade to future versions of Data Analyzer. Report heading on the Analyze tab. click the name of the color scheme. Report sub-heading on the Analyze tab. If blank. Data Analyzer looks for the images in the default image directory. Name of the color scheme directory where you plan to store the color and image files. enter file and directory information for color scheme images: ♦ ♦ ♦ ♦ Images Directory. If you modify a predefined color scheme. It also displays the directory for the images and the URL for the background. enter the following URL in the Logo Image URL field: http://monet. 2. use the forward slash (/) as a separator. For more information about hexadecimal color codes. if the host name of the web server where you have the logo file is http://monet. 4. To edit a predefined color scheme: 1. The color scheme uses the hexadecimal color codes for each display item. port 7001.gif The URL can point to a logo file in the Data Analyzer machine or in another web server. login.

Click Close to close the Color Scheme Preview window. copy your logo and image files into the new directory: /custom/images/standard/color/CompanyColor 76 Chapter 9: Managing System Settings . Step 1. Analyze. XML Export/Import. click Preview. System Management. Display Items in the Color Scheme Page Display Item Section Odd Table Row Even Table Row Selected Rows Primary Navigation Tab Colors Secondary Navigation Colors Description Background color for sections such as forms on the Administration tab. Copy your image files into the new folder. Create. Make sure Data Analyzer can access the images to use with the color scheme. Use the same color in Section for the Selected field in Tab Colors so that color flows evenly for each tab under the Primary Navigation tab. Menu items on the Administration tab. Tabs include items such as the Define Report Properties tab in Step 5 of the Create Report wizard and the toolbar on the Analyze tab. Alerts. To create a new color scheme folder: 1. Create a New Color Scheme Folder Create a folder in the color schemes directory and copy the image files you want to use to this folder. and tabs with drop-down lists. Rows you select in the report table or on tabs such as the Find tab. 6. pop-up windows. 3. Administration. Create a new color scheme in Data Analyzer and use the new folder as the Images Directory. 7. Odd rows in a list. To create a new color scheme folder. if you want to create a /CompanyColor directory for your new color scheme. Creating a Color Scheme You can create a Data Analyzer color scheme. Real-time Configuration. you can use your own images and logos. Add the directory and files for the new color scheme under the default image directory. The name of the color scheme folder can be up to 10 characters. Create a folder for the images and logo. including Schema Design. Even rows in a list. For example. The Color Scheme Preview window displays an example of the way Data Analyzer will appear with the color scheme. Find. Scheduling.Table 9-1. navigate to the EAR directory. Click OK to save your changes. Button Colors Tab Colors 5. and Manage Account tabs. Buttons in Data Analyzer. and Access Management. 2. Tabs under the Primary Navigation tab. complete the following steps: 1. View. Create a folder for the new color scheme: /custom/images/standard/color/ 2. When you create a color scheme. Create a folder for the images and make sure it contains the new images. To preview the choices. To create a color scheme.

in GIF or JPG format. set the colors you want to use for the color scheme and provide the new folder name for the images. For more information about display items on the Color Scheme page. After you set up the folder for the images to use in a new color scheme. The Color Scheme page appears. Click Apply. Data Analyzer uses the selected color scheme as the default for the repository. In the Background Image URL field. the image files for your color scheme must have the same names and format as the image files for the predefined color schemes. see “HTML Hexadecimal Color Codes” on page 121. In the Logo Image URL field. Click Add. 3. Since Data Analyzer references the image files to display them in Data Analyzer. select Default next to the color scheme name. Data Analyzer uses the Informatica color scheme. enter the file name of the background image you want to use. 4. 3. Selecting a Default Color Scheme You can select a default color scheme for Data Analyzer. 6. 2. Enter the name and description of the new color scheme. In the Images Directory field. Click OK to save the new color scheme. For more information about hexadecimal color codes. The Color Schemes and Logos page displays the list of available color schemes. Make sure the image file is saved in the color scheme folder you created earlier. To create a new color scheme in Data Analyzer: 1. If you do not specify a color scheme for a user or group. Data Analyzer uses a default set of colors that may not match the colors of your image files. To set the default color scheme for Data Analyzer. Create a New Color Scheme in Data Analyzer On the Color Schemes page. Click Administration > System Management > Color Schemes and Logos. you can create the color scheme in Data Analyzer and use the new color scheme directory. enter the file name of the logo image to use. Managing Color Schemes and Logos 77 . enter the name of the color scheme folder you created. enter the file name of the login page image to use. 2. Step 2. The new color scheme folder must exist in the EAR directory for Data Analyzer to access it. 5. All file names are case sensitive. Click Preview to preview the new color scheme colors. If you do not set up new colors for the color scheme. Enter the hexadecimal codes for the colors you want to use in the new color scheme. see Table 9-1 on page 75. 7. Click Administration > System Management > Color Schemes and Logos.You must have image files for all buttons and icons that display in Data Analyzer. The background and logo image files can have file names that you specify. 9. In the Login Page Image URL field. 8. To select a default color scheme: 1. 10. The Color Schemes and Logos page appears.

and save the user log. informational. the color scheme for the primary group takes precedence over the other group color schemes. and debugging messages about the size of the Data Analyzer global cache. In the Query Results area. 4. Click Administration > System Management > Color Schemes and Logos. Remote host. 78 Chapter 9: Managing System Settings . The date and time the user logged out based on the machine running the Data Analyzer server. The user log lists the following information: ♦ ♦ ♦ ♦ ♦ Login name. Click OK to close the dialog box. Logoff time. 7. Lists error. The date and time the user logged in based on the machine running the Data Analyzer server. To assign additional users or groups. To assign a color scheme: 1. the user requesting the activity. To assign the color scheme to a user or group. repeat steps 3 to 5. Lists the location and login and logout times for each user. you can track user activity in Data Analyzer. The host name accessing Data Analyzer when available. ♦ ♦ ♦ Viewing the User Log With the user log. Click the name of the color scheme you want to assign. Data Analyzer stores the user log entries in the repository. 5. Use the search options to produce a list of users or groups. Click OK to save the color scheme. and the duration of the request and activity. If the user does not have a primary group. The name of the user accessing Data Analyzer. Lists Data Analyzer activity. Lists all repository connection activities. Activity log. Global cache log. 3. The IP address accessing Data Analyzer when available. Assign specific color schemes when you want a user or group to use a color scheme other than the default color scheme. the objects used for the activity. and click Add. Login time. Remote address. informational. Lists error. Data Analyzer uses the default color scheme. select the users or groups you want to assign to the color scheme. You can also configure it to log report queries. 6. and debugging messages. When you assign a user and its group to different color schemes. activity type. You can assign color schemes to users and groups when you edit the color scheme. the user color scheme takes precedence over the group color scheme. When a user belongs to more than one group. JDBC log. You can also assign color schemes when you edit the user or group on the Access Management page. including the success or failure of the activity. warning.Assigning a Color Scheme You can assign color schemes to users and groups. The Assign Color Scheme window appears. clear. click Edit. System log. You can view. 2. Managing Logs Data Analyzer provides the following logs to track events and information: ♦ ♦ User log. warning.

such as web. 2. DB access. By default. such as report. The type of object requested. The identification number of the activity. The difference between login and logout times for each user. User role. such as Execute or Update. The source type of the activity request. Request ID.) The SQL statement used to run a report. see “Configuration Files” on page 129.000 rows in the user log. Activity. you can track the activity requests for your Data Analyzer server. (XML file only. hold the pointer over the user name. Data Analyzer clears all entries except for users who have logged in during the past 24 hours and have not yet logged off. The Data Analyzer user requesting the activity. 2. duration displays the length of time the user has been logged into Data Analyzer. User name. Click Clear. (XML file only. Data Analyzer deletes the log entries from the repository. To clear the user log: 1.properties. Start time. not just the currently displayed rows. Clear the activity log on a regular basis to optimize repository performance. Object name. The identification number of the request that the activity belongs to. When you clear the user log. To view the role of the user. You can clear the Data Analyzer user log. such as the number of requests to view or run reports. By default. The status of the activity. Configuring and Viewing the Activity Log With the activity log. Managing Logs 79 . or scheduler. Click Administration > System Management > User Log. hold the pointer over the user name. The name of the object requested.properties. Duration.user. Click Administration > System Management > User Log. Object type. Use this statistic to optimize database performance and schedule reports. You can change the number of rows by editing the value of the logging. If you sort the user log by a column. Saving and Clearing the User Log You can save the user log to an XML file.♦ ♦ Duration. Status. Data Analyzer sorts on all user log data. To save a user log: 1. To view the role of the user. Tables. Click Save. Data Analyzer stores the activity log entries in the repository. The time the user issued the activity request. Source. You might save a user log before clearing it to keep a record of user access. User role. The requested activity. The role of the user. The overall time in milliseconds takes to perform the request. and then follow the prompts to save the log to disk. Data Analyzer displays up to 1.maxRowsToDisplay property in DataAnalyzer. The time in milliseconds Data Analyzer takes to send the activity request to the data warehouse. For more information about editing DataAnalyzer. To view the user log.) The tables used in the SQL statement for a report. API. SQL. click Administration > System Management > User Log. the activity log tracks the following information: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Activity ID. such as Success or Failure. If the user has not logged out.

Click Clear. This additional information appears in the XML file generated when you save the activity log. and then follow the prompts to save the log to disk. To clear the activity log: 1. You might save the activity log to file before you clear it to keep a record of Data Analyzer activity. If you sort the activity log by a column. 80 Chapter 9: Managing System Settings . You can clear the activity log of all entries to free space and optimize repository performance. Data Analyzer displays up to 1. Configuring the System Log Data Analyzer generates a system log file named ias. click Administration > System Management > Activity Log. Data Analyzer logs the additional details. Click Administration > System Management > Log Configuration.activity. You can change the name of the log file and the directory where it is saved by editing the log4j. not just the currently displayed rows. To save an activity log: 1. To view the information. To configure the activity log: 1. 2. the System log displays error and warning messages. You can choose to display the following messages in the system log: ♦ ♦ ♦ ♦ Errors Warnings Information Debug To specify the messages displayed in the system log file: Click Administration > System Management > Log Configuration. save the activity log to file.maxRowsToDisplay property in the DataAnalyzer.log which logs messages produced by Data Analyzer. Click SQL in the Activity Log area to log queries.To view the activity log.000 rows in the activity log. You can configure the activity log to provide the query used to perform the activity and the database tables accessed to complete the activity. You can change the number of rows by editing the value of the logging.xml file. By default. You might also save the activity log to view information about the SQL statements and tables used for reports.properties file. select both SQL and Tables. You can locate the system log file in the following directory: <PowerCenter_install folder>/server/tomcat/jboss/server/informatica/log/<Reporting Service Name> By default. Saving and Clearing the Activity Log You can save the activity log to an XML file. You can view the system log file with any text editor. Click Save. Data Analyzer sorts on all activity log data. Click Administration > System Management > Activity Log. When you clear the activity log. Click Administration > System Management > Activity Log. 2. Data Analyzer clears all entries from the log. To log the tables accessed in the query. 2.

2. modify the File parameter to include the path and file name: <param name=”File” value=”d:/Log_Files/mysystem. if you want to save the Data Analyzer system logs to a file named mysystem. see the PowerCenter Administrator Guide. Save the file. Locate the log4j. If you do not know the value for BaseDN. You use the LDAP settings in Data Analyzer to access contacts within the LDAP directory service when you send email from Data Analyzer.dir}/log/<Reporting Service Name>/ias.file property in the DataAnalyzer. Data Analyzer does not support a single backslash as a file separator.To configure the name and location of the system log file: 1. you must provide a value for the BaseDN property. enter the Base distinguished name entries for your LDAP directory. The Base distinguished name entries define the type of information that is stored in the LDAP directory.server. Access LDAP directory contacts. You can use LDAP in the following ways: ♦ ♦ Authentication.logging. contact your LDAP system administrator. users can email reports and shared documents to LDAP directory contacts.home.log"/> 3.log in a folder called Log_Files in the D: drive. You use the PowerCenter LDAP authentication to authenticate the Data Analyzer users and groups. If you installed JBoss Application Server using the PowerCenter installer.properties.jboss. Configuring the JDBC Log Data Analyzer generates a JDBC log file. Open the file with a text editor and locate the following lines: <appender name="IAS_LOG" class="org. you can add the LDAP server on the LDAP Settings page. After you set up the connection to the LDAP directory service. locate the JDBC log file in the following directory: <PowerCenter_install folder>/server/tomcat/jboss/bin/ You can change the name of the file and the directory where it is saved by editing the jdbc. For example.log. Your changes will take affect in Data Analyzer within several minutes.append property in DataAnalyzer.log”/> 4. In the BaseDN property. You can also determine whether Data Analyzer appends data to the file or overwrites the existing JDBC log file by editing the jdbc. Modify the value of the File parameter to specify the name and location for the log file.appender. For more information about LDAP authentication. You can view the log file with any text editor.xml file in the following directory: <PowerCenter_install folder>/server/tomcat/jboss/server/informatica/ias/<Reporting Service Name>/META-INF The above folder is available after you enable the Reporting Service and the Data Analyzer instance is started. If you specify a path.log.properties file. When you add an LDAP server.DailyRollingFileAppender"> <param name="File" value="${jboss. Managing LDAP Settings 81 . Managing LDAP Settings Lightweight Directory Access Protocol (LDAP) is a set of protocols for accessing information directories. use the forward slash (/) or two backslashes (\\) in the path as the file separator. To access contacts in the LDAP directory service.

Click OK to save the changes. If you do not know the BaseDN.If you use Microsoft Active Directory as the LDAP directory. To modify the settings of an LDAP server. contact your LDAP system administrator.company. Table 9-2 lists the LDAP server settings you can enter: Table 9-2. The LDAP Settings page appears. Authentication System Name System Password 4.com BaseDN: dc= company_name. System password for the LDAP server. Click Add.dc= company_name. URL for the server. 3. The following example lists the values you need to enter on the LDAP Settings page for an LDAP server running Microsoft Active Directory: Name: Test URL: ldap://machine. System name of the LDAP server. 82 Chapter 9: Managing System Settings . Contact your LDAP system administrator for the system name and system password. Required when using System authentication.dc=com System Password: password The following example lists the values you need to enter on the LDAP Settings page for an LDAP server running a directory service other than Microsoft Active Directory: Name: Test URL: ldap:// machine. LDAP Server Settings Setting Name URL BaseDN Description Name of the LDAP server you want to configure.domain. If your LDAP server requires system authentication. click the name of the LDAP server on the LDAP Settings page.com BaseDN: dc=company_name. Required when using System authentication.cn=users. 2.com Base distinguished name entry identifies the type of information stored in the LDAP directory.dc=com Authentication: Anonymous To add an LDAP server: 1.dc=com Authentication: System System Name: cn=Admin. You must enter a valid system name and system password for the LDAP server. select System.company. Authentication method your LDAP server uses. you must choose System authentication as the type of authentication on the LDAP Settings page. Enter the following information. Click Administration > System Management > LDAP Settings. Use the following format: ldap://machine. Select System if you use Microsoft Active Directory as an LDAP directory. Select Anonymous if the LDAP server allows anonymous authentication.

Allows users to register an SMS/Text pager or phone as an alert delivery device. The mail server you configure must support Simple Mail Transfer Protocol (SMTP). In the Mail Server field. Click Apply. you must configure SMS/Text messaging. Click Administration > System Management > Delivery Settings. enter the URL for the proxy server. Click Administration > System Management > Delivery Settings. Allows Data Analyzer users to email reports and shared documents. Configuring SMS/Text Messaging and Mobile Carriers To allow users to receive one-way SMS/Text message alerts on a phone or pager. Configuring the Mail Server The mail server provides outbound email access for Data Analyzer and users. see the Data Analyzer User Guide. Configuring the External URL The external URL links Data Analyzer with your proxy server. and receive email alerts. Managing Delivery Settings 83 . To configure the external URL: 1. To configure the mail server: 1. 3. Configure an external URL so that users can access Data Analyzer from the internet. Click Apply. With outbound mail server configured. Allows users to connect to Data Analyzer from the internet. The Delivery Settings page appears. 2. In the External URL field. enter the URL to the outbound mail server. 2. The Delivery Settings page appears. Depending on the mail server. To receive SMS/Text message alerts. For more information about using an SMS/Text pager or phone as an alert device.Managing Delivery Settings You can determine how users access Data Analyzer and which functions they can access with delivery settings. SMS/text messaging and mobile carriers. You can configure one outbound mail server at a time. Data Analyzer configures the following mobile carriers: ♦ ♦ ♦ ♦ ♦ ATT Cingular Nextel Sprint Verizon You can configure additional mobile carriers by entering connection information for the carriers. the users also need to select a mobile carrier. Enter the URL for the proxy server you configured during installation. 3. The URL must begin with http:// or https://. You can configure the following delivery settings: ♦ ♦ ♦ Mail server. you might need to create a mail server connector before configuring the mail server. users can email reports and shared documents. External URL.

84 Chapter 9: Managing System Settings . The version of the Java Virtual Machine (JVM). Click Add. Click Administration > System Management > Delivery Settings. in the Mobile Carriers task area. driver version. To add a mobile carrier. The Operating System section displays the operating system. If you do not know the domain and extension. For example. 3. The System Information section lists the Data Analyzer version and build. 4. enter the name and address for the mobile carrier. if the wireless email address for ATT is myusername@mobile. The Java vendor web site. phone number. see your wireless carrier documentation.net. and architecture of the machine hosting Data Analyzer. The version of the application server that runs Data Analyzer. The version of the Java Servlet API. and email address of the system administrator.att. Click Administration > System Management > Contact Information. The home directory of the JVM. 2. To view system information: Click Administration > System Management > System Information. Viewing System Information On the System Information page. database server type. In the Delivery Settings area. In the address field. The System Information page contains the following sections: ♦ System Information. Home. Operating System. To specify contact information: 1. Classpath. A list of the paths and files contained in the Java classpath system variable. The Delivery Settings page displays.To configure SMS/Text Messaging and mobile carriers: 1. Specifying Contact Information When a system problem occurs. Data Analyzer adds the mobile carrier to the list of mobile carriers. you enter mobile. The Java section displays the following information about the Java environment on the machine hosting Data Analyzer: − − − − − − − ♦ ♦ Application Server. Vendor URL. Click Apply. 3. Java Version. enter the domain and extension of the email address associated with your device.att. Vendor. You can specify contact information for the system administrator in the System Management Area. version. select SMS/Text Messaging. you can view information about Data Analyzer and the machine that hosts it. driver name. Servlet API.net. Java. 2. users may need to contact the system administrator. The Java vendor. repository version. database version. JDBC connection string. and user name. Enter the name.

When this option is selected. The Query Governing page appears. 2. Setting Query Rules at the Group Level You can specify query governing settings for all reports belonging to a specific group. Table 9-3 describes the system query governing rules you can enter: Table 9-3. To set up group query governing rules: 1. clear the Use Default Settings option. Setting Rules for Queries 85 . If a query returns more rows than the row limit. Data Analyzer uses the largest query governing setting from each group. Default is 600 seconds. Row Limit 3. Click Administration > System Management > Query Governing. unless you override them at the group. Maximum number of rows SQL returns for each query. Default is 20. Click Edit next to the group whose properties you want to modify. Click Apply.Setting Rules for Queries You can configure the time limit on each SQL query for a report. When you clear this option.000 rows. You may have more than one SQL query for the report. To set up group query governing rules: 1. System Query Governing Settings Setting Query Time Limit Report Processing Time Limit Description Maximum amount of time for each SQL query. Data Analyzer displays a warning message and drops the excess rows. In the Query Governing section. Maximum amount of time allowed for the application server to run the report. Click Administration > Access Management > Groups. Setting Query Rules at the System Level You can specify the query governing settings for all reports in the repository. Enter the query governing settings you want to use. 4. These settings apply to all reports. the time limit on processing a report. and the maximum number of rows that each query returns. If a user belongs to one or more groups in the same level in the group hierarchy. or report level. user. 3. Default is 240 seconds. Data Analyzer uses the query governing settings entered on this page. Query governing settings for the group override system query governing settings. 2. you must log out of Data Analyzer and log in again for the new query governing settings to take effect. You can set up these rules for querying at the following levels: ♦ ♦ ♦ ♦ System Group User Report When you change the system query governing setting or the query governing setting for a group or user. Enter the query governing rules. Data Analyzer uses the system query governing settings. Report Processing Time includes time to run all queries for the report.

For more information about each setting, see Table 9-3 on page 85.
5.

Click OK. Data Analyzer saves the group query governing settings.

Setting Query Rules at the User Level
You can specify query governing settings for all reports belonging to a specific user. Query governing settings for the user override group and system query governing settings.
To set up user query governing rules: 1. 2. 3.

Click Administration > Access Management > Users. Click the user whose properties you want to modify. In the Query Governing section, clear the Use Default Settings option. When you clear this option, Data Analyzer uses the query governing settings entered on this page. When this option is selected, Data Analyzer uses the query governing settings for the group assigned to the user.

4.

Enter the query governing settings you want to use. For more information about each setting, see Table 9-3 on page 85.

5.

Click OK. Data Analyzer saves the user query governing settings.

Query Governing Rules for Users in Multiple Groups
If you specify query governing settings for a user, Data Analyzer uses the query governing setting when it runs reports for the user. If you do not specify query governing settings for a user, Data Analyzer uses the query governing settings for the group that the user belongs to. If a user belongs to multiple groups, Data Analyzer assigns the user the least restrictive query governing settings available. Data Analyzer ignores groups with the system default query governing settings. For example, you have not specifically configured query governing settings for a user. The user belongs to three groups with the following query governing settings:
Group Group 1 Group 2 Group 3 Row Limit 25 rows Query Time Limit 30 seconds

Default query governing settings 18 rows 120 seconds

Data Analyzer does not consider Group 2 in determining the group query governing settings to use for the user reports. For the row limit, Data Analyzer uses the setting for Group 1 since it is the least restrictive setting. For query time limit, Data Analyzer uses the setting for Group 3 since it is the least restrictive setting.

Setting Query Rules at the Report Level
You can specify query governing settings for a specific report. Query governing settings for a specific report override group, user, and system query governing settings.
To set up report query governing rules: 1. 2. 3.

Click the Find tab. Click the report whose properties you want to modify. Click Edit.

86

Chapter 9: Managing System Settings

4. 5. 6.

Click Publish. On the Report Properties tab, click More Options. In the Query Governing section, clear the Use Default Settings option. When you clear this option, Data Analyzer uses the query governing settings entered on this page. When this option is selected, Data Analyzer uses the query governing settings for the user.

Setting Rules for Queries

87

7.

Enter the query governing settings you want to use. For more information about each setting, see Table 9-3 on page 85.

8.

Click Save.

Configuring Report Table Scroll Bars
You can configure report tables to appear with a scroll bar. When you enable the Show Scroll Bar on Report Table option, Data Analyzer displays a scroll bar when data in a report table extends beyond the size of the browser window. When the option is disabled, you use the browser scroll bar to navigate large report tables. By default, Data Analyzer displays scroll bars in report tables.
To change report table scroll bar display: 1.

Click Administration > System Management > Report Settings. The Report Settings page appears.

2. 3.

To allow scroll bars, select Show Scroll Bar on Report Table. To disable scroll bars, clear the option. Click Apply.

Configuring Report Headers and Footers
In the Header and Footer page, you can configure headers and footers for reports. You can configure Data Analyzer to display text, images, or report information such as report name. Headers and footers display on the report when you complete the following report tasks:
♦ ♦ ♦ ♦ ♦

Print. Headers and footers display in the printed version of the report. Export. Headers and footers display when you export to an HTML or PDF file. Broadcast. Headers and footers display when you broadcast a report as an HTML, PDF, or Excel file. Archive. Headers and footers display when you archive a report as an HTML, PDF, or Excel file. Email. Headers and footers display when you email a report as an HTML or PDF file.

You can display text or images in the header and footer of a report. When you select the headers and footers to display, preview the report to verify that the headers and footers display properly with enough spaces between text or images. Table 9-4 lists the options you can select to display in the report headers and footers:
Table 9-4. Display Options for Report Headers and Footers
Header/Footer Left Header Center Header Right Header Display Options Text or image file. Text. Text.

88

Chapter 9: Managing System Settings

Date when the report was last updated. Data Analyzer does not display any image for the report header or footer. broadcast. or select report property to display. Data Analyzer shrinks the font to fit the text in the allotted space by default.com. By default.HeaderFooter. . You can use the PDF. Text and Page Number.properties file to determine how Data Analyzer handles long headers and footers. if the host name of the web server where you saved the Header_Logo. To configure report headers and footers: 1. you must update the images in the EAR directory. .PaintersInc. Select an option and enter text. Data Analyzer displays the specified name in the footer. Date and time when you print. enter the complete URL for the image when you configure the header or footer. enter the following URL: http://monet. If you want to modify or use a new image for the left header or right footer.com:7001/Header_Logo.ShrinktoWidth property in the DataAnalyzer. .gif If Data Analyzer cannot find the header or footer image in the color scheme directory or the URL. archive.Name. The report header and footer image files are stored with the color scheme files in the EAR directory. Name of the report.Printed On. If you want to use an image file in a different location. Center Footer Right Footer The image files you display in the left header or the right footer of a report can be any image type supported by your browser.Last Update. If a user specifies a first name. Name of the user. Display Options for Report Headers and Footers Header/Footer Left Footer Display Options One or more of the following report properties: . You can also configure Data Analyzer to keep header and footer text the configured font size. The Report Header and Footer page appears. Select an option and enter text to display. Or select to display both. For example.User Name. Enter the text or image file name to display. Data Analyzer looks for the header and footer image files in the image file directory for the current Data Analyzer color scheme. Users can specify their names on the Manage Account tab. Select report properties to display. allowing Data Analyzer to display only the text that fits in the header or footer. export. Text or image file.PaintersInc. or last name. middle name.gif image file is http://monet. or email the report. Click Administration > System Management > Header and Footer. When you enter a large amount of text in a header or footer. Select to display text or image.Table 9-4. port 7001. Configuring Report Headers and Footers 89 .

To use text for left headers. 3. The department name appears in the list in the Departments area. To use text for the right footer. Click Add. 6. To use an image for the right footer. 2. Click Add. click Apply to set the report header and footer. see Table 9-4 on page 88. specify the complete URL. To use an image for the left header. 4. enter the name of the category. 5. 5. Configuring Departments and Categories You can associate repository objects with a department or category to organize repository objects. Click OK. 90 Chapter 9: Managing System Settings . For left footers. Click Preview to see how the report will look with the headers and footers you selected. Adobe Acrobat launches in a new browser window to display a preview of the report. To configure department and category: 1. For more information about the header and footer display options. The category name appears in the list in the Categories area. select the lower field and enter the name of the file to use. 4. select the footer you want to display. You might use category names to organize repository objects according to object characteristics. Or click Cancel to discard the changes to the headers and footers. enter the name of the department. Data Analyzer looks for the header and footer images in the image directory for the color scheme. If the image is not in the default image directory. Associating repository objects with a department or category can also help you search for these objects on the Find tab. select the top field and enter the text to display. such as Quarterly or Monthly. In the Categories area. such as Human Resource and Development. close the preview window and click Preview again to see the new report header and footer. On the Report Header and Footer page. select the headers you want to display and enter the header text. The Categories Departments page appears.2. You might use department names to organize repository objects according to the departments in your organization. 3. you can choose properties specific to the report. 6. Close the preview window. In the Departments area. You can associate the category or department you created with repository objects. select the lower field and enter the name of an image file in the Data Analyzer EAR file or specify a URL for the image. Data Analyzer saves the department or category names you added. To configure report headers. select the top field and enter the text to use. To configure report footers. Click Administration > System Management > Metadata Configuration. Note: If you make more changes in the report header and footer configuration.

<init-param> <param-name> InfUserAdminUIConfigurationStartup. 6.Configuring Display Settings for Groups and Users By default. Note: The web.xml file with a text editor and locate the line containing the following property: showSearchThreshold The value of the showSearchThreshold property is the number of groups or users Data Analyzer displays without providing the Search box. Configuring Display Settings for Groups and Users 91 .000. refine the search criteria. useradmin. If Data Analyzer returns more than 1. Data Analyzer displays a Search box so you can find the group or user you want to edit.ias. Default is 100.showSearchThreshold </param-name> <param-value>100</param-value> </init-param> 3. To change group or user display options in web. Change the value of the showSearchThreshold property according to your requirements.xml file is stored in the EAR directory.informatica. Back up the web. Restart Data Analyzer. Default is 1.searchLimit </param-name> <param-value>1000</param-value> </init-param> 5. 2.xml file before you modify it. Data Analyzer provides the following properties in a file named web. Open the /custom/properties/web. 4. Determines the number of groups or users Data Analyzer displays before displaying the Search box.com. useradmin.com. searchLimit. if you have more than 100 groups or users.xml so you can configure the user or group display according to your requirements: ♦ ♦ showSearchThreshold.xml: 1.informatica.000 groups or users in the search results. You can customize the way Data Analyzer displays users or groups. Change the value of the searchLimit property according to your requirements.xml. <init-param> <param-name> InfUserAdminUIConfigurationStartup. Determines the maximum number of groups or users in the search results before you must refine the search criteria. Save and close web.ias. Locate the line containing the following property: searchLimit The value of the searchLimit property is the maximum number of groups or users in the search result before you must refine the search criteria.

92 Chapter 9: Managing System Settings .

If you need additional information in a report. You can add charts or indicators. They include details on Data Analyzer usage and report schedules and errors. Administrator’s Dashboard The Administrator’s Dashboard displays the indicators associated with the administrative reports. On the Administrator’s Dashboard. Provides information on the number of users who logged in for the day. the number of reports accessed in each hour for the day.CHAPTER 10 Working with Data Analyzer Administrative Reports This chapter includes the following topics: ♦ ♦ ♦ Overview. You can access all administrative reports in the Data Analyzer Administrative Reports public folder under the Find tab. you can modify it to add metrics or attributes. After you set up the Data Analyzer administrative reports. 93 . or change the format of any report. 93 Setting Up the Data Analyzer Administrative Reports. They also require a data connector that includes the Data Analyzer administrative reports data source and operational schema. 97 Overview Data Analyzer provides a set of administrative reports that enable system administrators to track user activities and monitor processes. 94 Using the Data Analyzer Administrative Reports. They require a data source that points to the Data Analyzer repository. You can view the administrative reports in two areas: ♦ ♦ Administrator’s Dashboard. you can view and use the reports just like any other set of reports in Data Analyzer. The Data Analyzer administrative reports use an operational schema based on tables in the Data Analyzer repository. The reports provide a view into the information stored in the Data Analyzer repository. Data Analyzer Administrative Reports folder. and any errors encountered when Data Analyzer runs cached reports. The Administrator’s Dashboard has the following containers: ♦ Today’s Usage. you can quickly see how well Data Analyzer is working and how often users log in. You can enhance the reports to suit your needs and help you manage the users and processes in Data Analyzer more efficiently.

Select the server type of your Data Analyzer repository. 5. click Add. Click Administration > Schema Design > Data Sources. you can skip this step and use the existing data source for the administrative reports. you can set up the administrative reports on Data Analyzer. Lists the cached reports in Data Analyzer and when they are scheduled to run next. Add the Data Source to a Data Connector” on page 95. 2. and the longest running cached reports for the current month. Provides a report on the Data Analyzer users who have never logged in. The Data Source page appears. Admin Reports. Set Up a Data Source for the Data Analyzer Repository The administrative reports provide information on the Data Analyzer processes and usage. Future Usage. For more information. and run reports from this folder. the longest running on-demand reports. For more information about. 4. For more information. Create a data source for the Data Analyzer repository. To create the repository data source: 1. The administrative reports display information from the Data Analyzer repository. Add the repository data source to a data connector. see “Step 1. see “Step 3. 4. Also provides reports on the most and least accessed reports for the year. Data Analyzer Administrative Reports Folder The Data Analyzer Administrative Reports folder stores all the administrative reports. You need a data source to connect to the repository. see “Step 2. and then add the data source to a data connector. 3. Import the administrative reports to the Data Analyzer repository. you need a data connector that contains the data source to the repository. Add the administrative reports to a schedule. Add the Administrative Reports to Schedules” on page 96. Import the Data Analyzer Administrative Reports” on page 95. On the Data Sources page. After you create a Reporting Service in the PowerCenter Administration Console and the corresponding Data Analyzer instance is running properly.♦ ♦ ♦ Historical Usage. Import the XML files in the <PowerCenter_install folder>/DA-tools/AdministrativeReports folder to the Data Analyzer repository. Enter a name and description for the data source. Setting Up the Data Analyzer Administrative Reports Informatica ships a set of prepackaged administrative reports for Data Analyzer. 2. Select JDBC Data Source. Set Up a Data Source for the Data Analyzer Repository” on page 94. For more information. To have the reports and indicators regularly updated. Displays the users who logged in the most number of times during the month. 94 Chapter 10: Working with Data Analyzer Administrative Reports . complete the following steps: 1. You must enable the Reporting Service and access the Data Analyzer URL to set up the administrative reports. you can run the administrative reports on specific schedules. The information comes from the Data Analyzer repository. 3. You can view. see “Step 4. Step 1. open. To set up the administrative reports. To run the administrative reports. Note: If you have a data source that points to the Data Analyzer repository. You must create a data source that points to the Data Analyzer repository.

Data Analyzer provides JDBC drivers to connect to the Data Analyzer repository and data warehouse. 8. Test the connection. see “Importing Objects to the Repository” on page 49. Data Analyzer does not support a Teradata repository. The server type list includes the following databases: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Oracle. Setting Up the Data Analyzer Administrative Reports 95 . Data Analyzer uses the system data connector to connect to all the data sources required for Data Analyzer reports. Teradata. add the administrative reports data source to the system data connector. For more information about data connectors. Other. Import the Data Analyzer Administrative Reports Before you import the Data Analyzer administrative reports. DB2 (OS/390). To add the administrative reports data source to the system data connector: 1. and database-specific global variables that you need to run the administrative reports. When you select the server type. In the Additional Schema Mappings section. Data Analyzer supplies the driver name and connection string format for the JDBC drivers that Data Analyzer provides. Add the Data Source to a Data Connector Data Analyzer uses a data connector to connect to a data source and read the data for a report. click Add. see the Data Analyzer Schema Designer Guide. If you have several data connectors and you want to use a specific data connector for the administrative reports. Click Administration > Schema Design > Data Connectors. 2. Click OK. Import the XML files under the <PowerCenter_install folder>/DA-tools/AdministrativeReports folder. DB2 (AS/400). add the administrative reports data source to the specific data connector. The Data Connectors page appears. If Data Analyzer does not have a data connector. you must create one before running the Data Analyzer administrative reports. When you select Other. 6. If the connection fails. you must provide the driver name and connection string. Customize the JDBC connection string with the information for your Data Analyzer repository database. ensure that the Reporting Service is enabled and the Data Analyzer instance is running properly. Select to connect to a Microsoft SQL Server repository. Click the name of the system data connector. Step 3. Step 2. Consult your database administrator if necessary. To enable Data Analyzer to run the administrative reports. schedules. 3. Enter the user name and password to connect to the repository database. Sybase ASE. SQL Server. Select if you want to use a different driver or you have a repository that requires a different driver than those provided by Data Analyzer. DB2. Data Analyzer does not support a DB2 repository on AS/400. 9. Select to connect to a Sybase repository. Typically. Select to connect to an IBM DB2 repository. verify that the repository database information is correct. Select to connect to an Oracle repository. The XML files contain the schemas. For more information about importing XML files. Data Analyzer displays the properties of the system data connector. Data Analyzer does not support a DB2 repository on OS/390. dashboards. 7.

5. Select a report to add to a schedule. You can now run the administrative reports using the system data connector. The Midnight Daily schedule is one of the schedules created when you install Data Analyzer. Step 4. select Cached. 2. After you complete the steps to add the reports to the schedules. In the folders section of the Find tab. 7. After you import all the necessary objects for the administrative reports. Save the report. verify that the cached reports are assigned to the appropriate schedules. On the Properties tab. 6. 7. In the Data Source list. To add the administrative reports to schedules: 1. 5. select PA_Reposit and click Add >>. The report appears in the Create Report wizard. Add the Administrative Reports to Schedules Data Analyzer provides a set of schedules that you can use to run the administrative reports on a regular basis. 8. 4. Locate and click the folder named Data Analyzer Administrative Reports. The public folder named Data Analyzer Administrative Reports contains the administrative reports. The PA_Reposit operational schema is one of the schemas installed by the PowerCenter Reports installer. Repeat steps 1 to 8 to verify that the following administrative reports are assigned to the appropriate schedules: Report Todays Logins Todays Report Usage by Hour Top 5 Logins (Month To Date) Top 5 Longest Running On-Demand Reports (Month To Date) Top 5 Longest Running Scheduled Reports (Month To Date) Total Schedule Errors for Today Schedule Hourly Refresh Hourly Refresh Midnight Daily Midnight Daily Midnight Daily Hourly Refresh The Hourly Refresh schedule is one of the schedules installed by the PowerCenter Reports installer. 96 Chapter 10: Working with Data Analyzer Administrative Reports . click Public Folders. Data Analyzer displays the additional schema mapping for the system data connector. Click Publish. 3. 6. In the Available Schemas section. Click OK. Click Add.Data Analyzer expands the section and displays the available schemas in the repository. you might want to review the list of reports in the Data Analyzer Administrative Reports folder to make sure that the cached reports have been added to the correct schedule. 4. and then select Hourly Refresh from the list of schedules. select the administrative reports data source you created earlier. Click the Find Tab. Click Edit. 9.

Top 5 Logins (Month To Date). Use this report to determine the users who logged in to Data Analyzer the most number of times in the current month. This on-demand report provides information about the reports accessed within the current month. listed in alphabetical order: ♦ ♦ Activity Log Details. Data Analyzer provides the following administrator reports. This report provides information about the number of reports accessed for each hour of the current day. It is the primary report for an analytic workflow. The report shows the list of 10 reports that users find most useful. Reports Accessed by Users Today. To review the schedule for a report in the Data Analyzer Administrative Reports folder. Use this on-demand report to view the activity logs. You can access this report from the Today’s Usage container on the Administrator’s Dashboard and from the Find Tab. you need to create a data source for the repository. the report provides detailed information about all reports accessed by any user in the current day. Top 5 Longest Running On-Demand Reports (Month To Date). You can access this report from the Admin Reports container on the Administrator’s Dashboard and from the Find Tab. Use this on-demand report to determine the 10 least used reports in the current calendar year. it displays access information for all reports in the repository. Data Analyzer updates this cached report based on the Hourly Refresh schedule. You can access this report from the Admin Reports container on the Administrator’s Dashboard and from the Find Tab. Todays Logins. You can access this report from the Today’s Usage container on the Administrator’s Dashboard and from the Find Tab. Data Analyzer updates this cached report based on the Midnight Daily schedule. Report Refresh Schedule. Report Activity Details for Current Month. You can also use it to determine whether an on-demand report needs to ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ Using the Data Analyzer Administrative Reports 97 . This report provides information about the next scheduled update for cached reports. Use this report to monitor the update time for various reports. It is the primary report for an analytic workflow.10. This report displays the average response time for the five longest-running on-demand reports in the current month to date. Data Analyzer updates this cached report based on the Hourly Refresh schedule. Todays Report Usage by Hour. Use this report to determine the reports most accessed by users in the current calendar year. Using the Data Analyzer Administrative Reports The Data Analyzer administrative reports are located in the Data Analyzer Administrative Reports public folder on the Find tab. You can access this report from the Historical Usage container on the Administrator’s Dashboard and from the Find Tab. It is the primary report for an analytic workflow. Data Analyzer updates this cached report based on the Hourly Refresh schedule. Bottom 10 Least Accessed Reports this Year. After you schedule the administrative reports. Use this report to get information on the reports accessed by users in the current day. You can also access these reports from the Administrator’s Dashboard. select a report and look at the Report Properties section. You can access this report from the Find tab. Use this report to determine the system usage for the current day. The report displays the user names and number of times each user logged in. When you run this report from the Find tab. You can view this report as part of the analytic workflow for the Todays Logins primary report or as a standalone report. Report Activity Details. Use this report to help you tune the database or web server. This report provides the login count and average login duration for users who logged in on the current day. Top 10 Most Accessed Reports this Year. Use this report to monitor the update time for various reports. View this report as part of the analytic workflows for several primary reports or as a standalone report. You can access this report from the Find tab. You can access this report from the Future Usage container on the Administrator’s Dashboard and from the Find Tab. When you run the Report Activity Details from the Find tab.

run on a schedule. You can access this report from the Historical Usage container on the Administrator’s Dashboard and from the Find Tab. Data Analyzer updates this cached report based on the Midnight Daily schedule.

Top 5 Longest Running Scheduled Reports (Month To Date). This report displays the time that Data Analyzer takes to display the five longest running cached reports in the current month to date. Use this report for performance tuning and for determining whether a cached report needs to run on demand. You can access this report from the Historical Usage container on the Administrator’s Dashboard and from the Find Tab. Data Analyzer updates this cached report based on the Midnight Daily schedule. Total Schedule Errors for Today. This report provides the number of errors Data Analyzer encountered when running cached reports. Use this report to monitor cached reports and modify them if necessary. You can access this report from the Today’s Usage container on the Administrator’s Dashboard and from the Find Tab. Data Analyzer updates this cached report based on the Hourly Refresh schedule. User Log Details. Use this on-demand report to view the user logs. You can access this report from the Find tab. User Logins (Month To Date). This report displays the number of times each user logged in during the month. Use this report to determine how often users log in to Data Analyzer. You can access this report from the Historical Usage container on the Administrator’s Dashboard and from the Find Tab. Users Who Have Never Logged On. This report provides information about users who have never logged in to Data Analyzer. Use this report to make administrative decisions about disabling accounts. You can access this report from the Admin Reports container on the Administrator’s Dashboard and from the Find Tab.

♦ ♦

98

Chapter 10: Working with Data Analyzer Administrative Reports

CHAPTER 11

Performance Tuning
This chapter includes the following topics:
♦ ♦ ♦ ♦ ♦

Overview, 99 Database, 99 Operating System, 101 Application Server, 106 Data Analyzer Processes, 111

Overview
Data Analyzer requires the interaction of several components and services, including those that may already exist in the enterprise infrastructure, such as the enterprise data warehouse and authentication server. Data Analyzer is built on JBoss Application Server and uses related technology and application programming interfaces (APIs) to accomplish its tasks. JBoss Application Server is a Java 2 Enterprise Edition (J2EE)compliant application server. Data Analyzer uses the application server to handle requests from the web browser. It generates the requested contents and uses the application server to transmit the content back to the web browser. Data Analyzer stores metadata in a repository database to keep track of the processes and objects it needs to handle web browser requests. You can tune the following components to optimize the performance of Data Analyzer:
♦ ♦ ♦ ♦

Database Operating system Application server Data Analyzer

Database
Data Analyzer has the following database components:
♦ ♦

Data Analyzer repository Data warehouse

99

The repository database contains the metadata that Data Analyzer uses to construct reports. The data warehouse contains the data for the Data Analyzer reports. The data warehouse is where the report SQL queries are executed. Typically, it has a very high volume of data. The execution time of the reports depends on how well tuned the database and the report queries are. Consult the database documentation on how to tune a high volume database for optimal SQL execution. The Data Analyzer repository database contains a smaller amount of data than the data warehouse. However, since Data Analyzer executes many SQL transactions against the repository, the repository database must also be properly tuned to optimize the database performance. This section provides recommendations for tuning the Data Analyzer repository database for best performance.
Note: Host the Data Analyzer repository and the data warehouse in separate database servers. The following

repository database tuning recommendations are valid only for a repository that resides on a database server separate from the data warehouse. If you have the Data Analyzer repository database and the data warehouse in the same database server, you may need to use different values for the parameters than those recommended here.

Oracle
This section provides recommendations for tuning the Oracle database for best performance.

Statistics
To ensure that the repository database tables have up-to-date statistics, periodically run the following command for the repository schema:
EXEC DBMS_STATS.GATHER_SCHEMA_STATS(ownname=><RepositorySchemaName>, cascade=>true,estimate_percent=>100);

Shared Pool and Database Cache Size
For optimal performance, set the following parameter values for the Data Analyzer repository database:
shared_pool_size = 100000000 (100 M) db_cache_size = 100000000 (100 M)

For more information about tuning an Oracle database, see the Oracle documentation.

User Connection
For an Oracle repository database running on HP-UX, you may need to increase the number of user connections allowed for the repository database so that Data Analyzer can maintain continuous connection to the repository. To enable more connections to the Oracle repository, complete the following steps: 1. At the HP-UX operating system level, raise the maximum user process (maxuprc) limit from the default of 75 to at least 300. Use the System Administration Manager tool (SAM) to raise the maxuprc limit. Raising the maxuprc limit requires root privileges. You need to restart the machine hosting the Oracle repository for the changes to take effect. 2. In Oracle, raise the values for the following database parameters in the init.ora file:
♦ ♦

Raise the value of the processes parameter from 150 to 300. Raise the value of the pga_aggregate_target parameter from 32 MB to 64 MB (67108864).

Updating the database parameters requires database administrator privileges. You need to restart Oracle for the changes to take effect. If the Data Analyzer instance has a high volume of usage, you may need to set higher limits to ensure that Data Analyzer has enough resources to connect to the repository database and complete all database processes.

100

Chapter 11: Performance Tuning

If you do not update table statistics periodically. Use the ulimit command to set the file descriptor limit.boulder. Linux limits the amount of memory and the number of memory segments that can be shared among applications to a reasonably small value. To change these parameters. You need to increase these values because the Java threads need to have access to the same area of shared memory and its resultant segments. Enlarging Shared Memory and Shared Memory Segments By default.local Operating System 101 . Enlarge the maximum open file descriptors.html?Open Microsoft SQL Server 2000 To ensure that repository database tables and indexes have up-to-date statistics. Operating System For all UNIX operating systems. enter the following commands as root on the machine where you install Data Analyzer: # echo "2147483648" > /proc/sys/kernel/shmmax # echo "250 32000 100 128" > /proc/sys/kernel/sem These changes only affect the system as it is running now. make sure the file descriptor limit for the shell running the application server process is set to at least 2048.nsf/RedbookAbstracts/sg246432. you need to make several changes to your Linux environment. You must modify basic system and kernel settings to allow the Java component better access to the resources of your system: ♦ ♦ ♦ Enlarge the shared memory and shared memory segments. The following recommendations for tuning the operating system are based on information compiled from various application server vendor web sites.IBM DB2 To ensure that the repository database tables have up-to-date statistics. you may encounter transaction deadlocks during times of high concurrency usage. Enlarge the maximum per-process open file descriptors. Linux To optimize Data Analyzer on Linux.com/Redbooks. Enter the following commands to make them permanent: # echo '#Tuning kernel parameters' >> /etc/rc. set the following parameter values for the Data Analyzer repository database: LOCKLIST = 600 MAXLOCKS=40 DBHEAP = 4000 LOGPRIMARY=100 LOGFILSIZ=2000 For more information about DB2 performance tuning. refer to the following IBM Redbook: http://publib-b. periodically run the sp_updatestats stored procedure on the repository schema.ibm. periodically run the following command for the repository schema: REORGCHK UPDATE STATISTICS on SCHEMA <DBSchemaName> Analysis of table statistics is important in DB2. For optimal performance.d/rc.

tcp_max_syn_backlog Suggested Values 1500 1024 8192 HP-UX You can tune the following areas in the HP-UX operating system to improve overall Data Analyzer performance: ♦ ♦ ♦ Kernel Java Process Network Kernel Tuning HP-UX has a Java-based configuration utility called HPjconfig which shows the basic kernel parameters that need to be tuned and the different patches required for the operating system to function properly.local Enlarging the Maximum Open File Descriptors Linux has a programmed limit for the number of files it allows to be open at any one time. By default.d/login Additional Recommended Settings Table 11-1 shows additional recommended settings for Linux operating system parameters: Table 11-1. Recommended Settings for Linux Parameters Linux Parameters /sbin/ifconfig lo mtu kernel.conf '* hard nofile 4096' >> /etc/security/limits.00.ipv4.www2.conf '* soft nofile 4096' >> /etc/security/limits.msgmni net. You can download the configuration utility from the following HP web site: http://h21007. Enter the following commands to make them permanent: # echo 'echo "65536" > /proc/sys/fs/file-max' >> /etc/rc.# echo 'echo "2147483648" > /proc/sys/kernel/shmmax' >> /etc/rc.1620. Increasing this limit removes any bottlenecks from all the Java threads requesting files.html The HPjconfig recommendations for a Java-based application server running on HP-UX 11 include the following parameter values: Max_thread_proc = 3000 Maxdsiz = 2063835136 Maxfiles=2048 Maxfiles_lim=2048 Maxusers=512 102 Chapter 11: Performance Tuning .d/rc. Enter the following command as root to increase the maximum number of open file descriptors: # echo "65536" > /proc/sys/fs/file-max These changes affect the system as it is currently running.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1. this is set to 4096 files. Enter the following commands as root to increase the maximum open file descriptors per process: # # # # echo echo echo echo '# Set soft and hard process file descriptor limits' >> /etc/security/limits.1701.local # echo 'echo "250 32000 100 128" > /proc/sys/kernel/sem' >> /etc/rc.d/rc.hp.conf 'session required /lib/security/pam_limits.local Enlarging the Maximum Per-Process Open File Descriptors Increase the maximum number of open files allowed for any given process.so' >> /etc/pam.d/rc.

hp. as shown in the following example: ndd -set /dev/tcp tcp_conn_req_max_q 16384 Tip: Use the netstat -s -P tcp command to view all available TCP-related parameters.com/hpux/onlinedocs/TKP-90203/TKP-90203. For more information about kernel parameters affecting Java performance. Set parameters in the /etc/system file. Set parameters on the network card. For more information about tuning the HP-UX kernel. The default value for the Java virtual machine instruction and data page sizes is 4 MB.html Java Process You can set the JVM virtual page size to improve the performance of a Java process running on an HP-UX machine. to set the tcp_conn_request_max parameter. use the following command: ndd -set /dev/tcp tcp_conn_request_max 1024 After modifying the settings. restart the machine.Ncallout=6000 Nfile=30000 Nkthread=3000 Nproc=2068 Note: For Java processes to function properly. see the HP documentation. Solaris You can tune the Solaris operating system to optimize network and TCP/IP operations in the following ways: ♦ ♦ ♦ Use the ndd command. Increase the value to 64 MB to optimize the performance of the application server that Data Analyzer runs on. Recommended ndd Settings for HP-UX ndd Setting tcp_conn_request_max tcp_xmit_hiwater_def tcp_time_wait_interval tcp_recv_hiwater_def tcp_fin_wait_2_timeout Recommended Value 16384 1048576 60000 1048576 90000 For example.0/native_threads/java Network Tuning For network performance tuning. use the ndd command to view and set the network parameters. see the document titled “Tunable Kernel Parameters” on the following HP web site: http://docs. it is important that the HP-UX operating system is on the proper patch level as recommended by the HPjconfig tool. Table 11-2 provides guidelines for ndd settings: Table 11-2. use the following command: chatr +pi64M +pd64M <JavaHomeDir>/bin/PA_RISC2. To set the JVM virtual page size. Operating System 103 . Setting Parameters Using ndd Use the ndd command to set the TCP-related parameters.

the hash table size. configure your operating system to have the appropriate number of file descriptors. Note: Restart the machine if you modify /etc/system parameters. Setting Parameters in the /etc/system File Each socket connection to the server consumes a file descriptor. the tcp_time_wait_interval parameter was called tcp_close_ wait_interval. holding these socket resources can have a significant negative impact on performance. The default value of this parameter on Solaris is four minutes. When many clients connect for a short period of time. Recommended /etc/system Settings for Solaris Parameter rlim_fd_cur rlim_fd_max tcp:tcp_conn_hash_size semsys:seminfo_semume semsys:seminfo_semopm *shmsys:shminfo_shmmax autoup Recommended Value 8192 8192 32768 1024 200 4294967295 900 104 Chapter 11: Performance Tuning . You might want to decrease this setting if the server is backed up with a queue of half-opened connections. Recommended ndd Settings for Solaris ndd Setting /dev/tcp tcp_time_wait_interval /dev/tcp tcp_conn_req_max_q /dev/tcp tcp_conn_req_max_q0 /dev/tcp tcp_ip_abort_interval /dev/tcp tcp_keepalive_interval /dev/tcp tcp_rexmit_interval_initial /dev/tcp tcp_rexmit_interval_max /dev/tcp tcp_rexmit_interval_min /dev/tcp tcp_smallest_anon_port /dev/tcp tcp_xmit_hiwat /dev/tcp tcp_recv_hiwat /dev/tcp tcp_naglim_def /dev/ce instance /dev/ce rx_intr_time /dev/tcp tcp_fin_wait_2_flush_interval Recommended Value 60000 16384 16384 60000 30000 4000 10000 3000 32768 131072 131072 1 0 32 67500 Note: Prior to Solaris 2. and other tuning parameters in the /etc/system file. Table 11-4 lists the /etc/system parameters that you can tune and the recommended values: Table 11-4.Table 11-3 lists the TCP-related parameters that you can tune and their recommended values: Table 11-3. Setting this parameter to a value of 60000 (60 seconds) has shown a significant throughput enhancement when running benchmark JSP tests on Solaris. Change the default file descriptor limits. This parameter determines the time interval that a TCP socket is kept alive after issuing a close call. To optimize socket performance.7.

see the Performance Management Guide on the IBM web site: http://publib16. Recommended /etc/system Settings for Solaris Parameter tune_t_fsflushr Recommended Value 1 *Note: Set only on machines that have at least 4 GB of RAM.Table 11-4.boulder. see the Solaris Tunable Parameters Reference Manual. Use the no and nfso commands to set the buffer sizes. add the commands to the /etc/rc. you can increase the TCP/IP or UDP buffer sizes. For more information about AIX tuning options. AIX If an application on an AIX machine transfers large amounts of data. Setting Parameters on the Network Card Table 11-5 lists the CE Gigabit card parameters that you can tune and the recommended values: Table 11-5. use the following command: /usr/sbin/no -o tcp_sendspace=262144 Table 11-6 lists the no parameters that you can set and their recommended values: Table 11-6.ibm. Recommended CE Gigabit Card Settings for Solaris Parameter ce:ce_bcopy_thresh ce:ce_dvma_thresh ce:ce_taskq_disable ce:ce_ring_size ce:ce_comp_ring_size ce:ce_tx_ring_size Recommended Value 256 256 1 256 1024 4096 For more information about Solaris tuning options.htm Operating System 105 . Recommended Buffer Size Settings for no Command for AIX Parameter tcp_sendspace tcp_recvspace rfc1323 tcp_keepidle Recommended Value 262144 262144 1 600 Table 11-7 lists the nfso parameters that you can set and their recommended values: Table 11-7.net file. to set the tcp_sendspace parameter. Recommended Buffer Size Settings for nfso Command for AIX Parameter nfs_socketsize nfs_tcp_socketsize Recommended Value 200000 200000 To permanently set the values when the system restarts.com/pseries/en_US/aixbman/prftungd/prftungd. For example.

5-doc/config/index. then the following message may appear in the log files: ERROR [ThreadPool] All threads are busy.bind. If not specified. For more 106 Chapter 11: Performance Tuning . Set the attribute to a value smaller than the value set for maxThreads. To tune the Servlet/JSP container. ♦ ♦ By default. If not specified. leading to a general slow down of Data Analyzer. Maximum number of unused request processing threads that can exist before the pool begins stopping the unused threads. the Windows 2000 default settings for the TCP/IP parameters are adequate to ensure optimal network performance. the parameter is set to 200. You can tune the Servlet/JSP container to make an optimal number of threads available to accept and process HTTP requests. Increasing the number of threads means that more users can use Data Analyzer concurrently. see the Apache Tomcat Configuration Reference on the Apache Tomcat website: http://tomcat.5 Servlet/JSP container. more concurrent users may cause the application server to sustain a higher processing load. However. Data Analyzer is configured to have a maximum of 250 request processing threads which is acceptable for most environments. leading to faster response times. Number of request processing threads initially created in the pool. If not specified. the parameter is set to 50. Application Server JBoss Application Server consists of several components.apache.A HTTP/1. If the number of threads is too low. The following are some of the JBoss Application Server components and recommendations for tuning parameters to improve the performance of Data Analyzer running on JBoss Application Server. Servlet/JSP Container JBoss Application Server uses the Apache Tomcat 5. modify the following configuration file: <JBOSS_HOME>/server/informatica/deploy/jbossweb-tomcat55. Decreasing the number of threads means that fewer users can use Data Analyzer concurrently.1 Connector on port 8080 --> <Connector port="8080" address="${jboss. Fewer concurrent users may alleviate the load on the application server. waiting. Maximum number of request processing threads that can be created in the pool. Data Analyzer may generate unexpected results if you modify properties that are not documented in this section. Usually.org/tomcat-5. For additional information about configuring the Servlet/JSP container. You may need to modify this value to achieve better performance.Windows Disable hyper-threading on a four-CPU Windows 200 machine to provide better throughput for a clustered application server in a high concurrency usage environment.html The Servlet/JSP container configuration file does not determine how JBoss Application Server handles threads. some users may need to wait for their HTTP request to be served. each of which has a different set of configuration files and parameters that can be tuned. which determines the maximum number of simultaneous requests that the Servlet/JSP container can handle.address}" maxThreads="250" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"/> The following parameters may need tuning: ♦ maxThreads. Please increase maxThreads Although the Servlet/JSP container configuration file contains additional properties.sar/server.xml The following is a typical configuration: <!-. minSpareThreads. the parameter is set to 4. You can also define and configure thread handling in the JBoss Application Server configuration files. maxSpareThreads. However.

Set the development parameter to false in a production installation. To avoid having the application server compile JSP scripts when they are executed for the first time. the JSP scripts must be compiled when they are executed for the first time. for an Oracle repository.informatica. you can tune the database connection pools.SID=prfbase8 </connection-url> <driver-class> com.jasper. The following is a typical configuration: <datasources> <local-tx-datasource> <jndi-name>jdbc/IASDataSource</jndi-name> <connection-url> jdbc:informatica:oracle://aries:1521. When set to true.apache. you can set the checkInterval parameter to specify when the JSPs are checked. Informatica ships Data Analyzer with pre-compiled JSPs.servlet. If you find that you need to compile the JSP files either because of customizations or while patching. Repository Database Connection Data Analyzer accesses the repository database to get metadata information. you can modify the following configuration file to optimize the JSP compilation: <JBOSS_HOME>/server/informatica/deploy/jbossweb-tomcat55. modify the JBoss configuration file: <JBOSS_HOME>/server/informatica/deploy/<DB_Type>_ds.xml. In production environment. set it to 600 seconds. Data Analyzer keeps a pool of database connections for the repository. This works only when the development parameter is set to true.jdbc.xml The name of the file includes the database type. checks for modified JSPs at every access. JSP Optimization Data Analyzer uses JavaServer Pages (JSP) scripts to generate content for the web pages used in Data Analyzer. db2 or other databases. see the JBoss Application Server documentation.JspServlet</servlet-class> <init-param> <param-name>logVerbosityLevel</param-name> <param-value>WARNING</param-value> <param-name>development</param-name> <param-value>false</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet> The following parameter may need tuning: ♦ development.sar/conf/web.information about configuring thread management on JBoss Application Server. ♦ checkInterval.oracle.OracleDriver </driver-class> Application Server 107 . <DB_Type> can be oracle. Checks for changes in the JSP files on an interval of n seconds. For example. For example: <param-name>checkInterval</param-name> <param-value>99</param-value> Note: Make sure that the checkInterval is not too low. the configuration file name is oracle_ds. To optimize Data Analyzer database connections. Typically. If you set the development parameter to true.xml The following is a typical configuration: <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org. To tune the repository database connection pool.

jboss.ejb. idle-timeout-minutes. EJB Container Data Analyzer uses Enterprise Java Beans extensively.plugins.ejb.BMT --> <interceptor transaction="Bean"> org. The following is a typical configuration <container-configuration> <container-name> Standard Stateless SessionBean</container-name> <call-logging>false</call-logging> <invoker-proxy-binding-name> stateless-rmi-invoker</invoker-proxy-binding-name> <container-interceptors> <interceptor>org. The max-pool-size value needs to be at least five more than the maximum number of concurrent users.ejb. There are also six message-driven beans (MDBs) used for scheduling and real-time processes.MetricsInterceptor</interceptor> <interceptor transaction="Container"> org.plugins.TxInterceptorCMT</interceptor> <interceptor transaction="Container" metricsEnabled="true"> org. After you use it.plugins. Set a higher value for idle-timeout-minutes.jboss.ProxyFactoryFinderInterceptor </interceptor> <interceptor> org.StatelessSessionInstanceInterceptor </interceptor> <!-. It may block other threads that require new connections.jboss. Stateless Session Beans For SLSBs. Length of time an idle connection remains in the pool before it is used. Maximum size of the connection pool. You can tune the EJB pool parameters in the following file: <JBOSS_HOME>/server/Informatica/conf/standardjboss.jboss.LogInterceptor</interceptor> <interceptor> org.plugins.vendor. Minimum number of connections in the pool. it consumes resources to check for idle connections and clean them out.ejb.resource. blocking-timeout-millis.plugins.jboss. max-pool-size.jdbc.xml.ejb. Each report needs a database connection.CMT --> <interceptor transaction="Container"> org.plugins.ejb. It has over 50 stateless session beans (SLSB) and over 60 entity beans (EB).<user-name>powera</user-name> <password>powera</password> <exception-sorter-class-name> org.StatelessSessionInstanceInterceptor </interceptor> <interceptor transaction="Bean"> 108 Chapter 11: Performance Tuning .SecurityInterceptor</interceptor> <!-. Maximum time in milliseconds that a caller waits to get a connection when no more free connections are available in the pool.jboss.jboss. because there may be several scheduled reports running in the background. the most important tuning parameter is the EJB pool. Since Data Analyzer accesses the repository very frequently.OracleExceptionSorter </exception-sorter-class-name> <min-pool-size>5</min-pool-size> <max-pool-size>50</max-pool-size> <blocking-timeout-millis>5000</blocking-timeout-millis> <idle-timeout-minutes>1500</idle-timeout-minutes> </local-tx-datasource> </datasources> The following parameters may need tuning: ♦ ♦ ♦ ♦ min-pool-size.ejb.adapter.jboss. it will contain at least the minimum number of pool-size connections.plugins. The pool is empty until it is first accessed.

connectionmanager.jboss.jboss.plugins. the number of active objects can exceed the <MaximumSize> if there are requests for more objects.jboss.TxInterceptorBMT</interceptor> <interceptor transaction="Bean" metricsEnabled="true"> org. Instead.jboss.CachedConnectionInterceptor </interceptor> </container-interceptors> <instance-pool> org. They may be tuned after you have completed proper iterative testing in Data Analyzer to increase the throughput for high concurrency installations: ♦ strictMaximumSize. strictTimeout. However.jboss.MessageDrivenInstanceInterceptor Application Server 109 .jboss.StatelessSessionInstancePool</instance-pool> <instance-cache></instance-cache> <persistence-manager></persistence-manager> <container-pool-conf> <MaximumSize>100</MaximumSize> </container-pool-conf> </container-configuration> The following parameter may need tuning: ♦ MaximumSize.plugins.jboss.ejb.MetricsInterceptor</interceptor> <interceptor> org.plugins. only the <MaximumSize> number of objects will be returned to the pool. Any subsequent requests will wait for an object to be returned to the pool.jboss.TxInterceptorCMT</interceptor> <interceptor transaction="Container" metricsEnabled="true"> org. the messaging system delivers messages to the MDB when they are available. If <strictMaximumSize> is set to false. You can set two other parameters to fine tune the EJB pool.ejb.plugins.jboss.plugins.MessageDrivenInstanceInterceptor </interceptor> <!-. These parameters are not set by default in Data Analyzer.plugins. the <strictMaximumSize> enforces a rule that only <MaximumSize> number of objects will be active.ProxyFactoryFinderInterceptor </interceptor> <interceptor>org.plugins.plugins.resource.plugins.ejb.LogInterceptor</interceptor> <interceptor>org. When the value is set to true.ejb.ejb.RunAsSecurityInterceptor </interceptor> <!-.CMT --> <interceptor transaction="Container"> org.xml The following is a typical configuration: <container-configuration> <container-name>Standard Message Driven Bean</container-name> <call-logging>false</call-logging> <invoker-proxy-binding-name>message-driven-bean </invoker-proxy-binding-name> <container-interceptors> <interceptor>org. To tune the MDB parameters.ejb. then <strictTimeout> is the amount of time that requests will wait for an object to be made available in the pool.jboss.ejb. Represents the maximum number of objects in the pool.jboss.ejb. If <strictMaximumSize> is set to true.ejb.plugins. then <MaximumSize> is a strict upper limit for the number of objects that will be created. If you set <strictMaximumSize> to true.BMT --> <interceptor transaction="Bean"> org.MetricsInterceptor </interceptor> <interceptor transaction="Container"> org. The main difference is that MDBs are not invoked by clients. ♦ Message-Driven Beans (MDB) MDB tuning parameters are very similar to stateless bean tuning parameters. modify the following configuration file: <JBOSS_HOME>/server/informatica/conf/standardjboss.org.ejb.

jboss.plugins.jboss.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT </interceptor> <interceptor transaction="Bean" metricsEnabled="true"> org. If <strictMaximumSize> is set to true.jboss.plugins. then <MaximumSize> is a strict upper limit for the number of objects that will be created.ejb.plugins.ejb.ejb.CachedConnectionInterceptor </interceptor> </container-interceptors> <instance-pool>org.EntityInstancePool 110 Chapter 11: Performance Tuning .jboss.connectionmanager.jboss.xml.ejb.jboss.EntityCreationInterceptor </interceptor> <interceptor>org.plugins.SecurityInterceptor </interceptor> <interceptor>org.ProxyFactoryFinderInterceptor </interceptor> <interceptor>org.plugins.EntityInstanceInterceptor </interceptor> <interceptor>org.plugins.ejb. Otherwise.jboss.plugins.plugins.ejb.ejb.LogInterceptor</interceptor> <interceptor>org.ejb.ejb.jboss. Enterprise Java Beans Data Analyzer EJBs use bean-managed persistence (BMP) as opposed to container-managed persistence (CMP).EntityReentranceInterceptor </interceptor> <interceptor> org.plugins. The EJB tuning parameters are in the following configuration file: <JBOSS_HOME>/server/informatica/conf/standardjboss.resource. if <strictMaximumSize> is set to false.plugins.ejb.jboss.</interceptor> <interceptor transaction="Bean"> org. only the <MaximumSize> number of objects will be returned to the pool. The following is a typical configuration: <container-configuration> <container-name>Standard BMP EntityBean</container-name> <call-logging>false</call-logging> <invoker-proxy-binding-name>entity-rmi-invoker </invoker-proxy-binding-name> <sync-on-commit-only>false</sync-on-commit-only> <container-interceptors> <interceptor>org.TxInterceptorCMT </interceptor> <interceptor metricsEnabled="true"> org. Represents the maximum number of objects in the pool.jboss.ejb.MetricsInterceptor</interceptor> <interceptor>org.plugins.resource.plugins.jboss.plugins.ejb.MessageDrivenInstancePool </instance-pool> <instance-cache></instance-cache> <persistence-manager></persistence-manager> <container-pool-conf> <MaximumSize>10</MaximumSize> </container-pool-conf> </container-configuration> The following parameter may need tuning: ♦ MaximumSize.ejb.jboss. the number of active objects can exceed the <MaximumSize> if there are requests for more objects.MetricsInterceptor</interceptor> <interceptor> org.jboss.jboss.jboss.EntityLockInterceptor </interceptor> <interceptor>org.EntitySynchronizationInterceptor </interceptor> </container-interceptors> <instance-pool>org. However.CachedConnectionInterceptor </interceptor> <interceptor> org.connectionmanager.

jboss.ejb.ejb. They may be tuned after you have completed proper iterative testing in Data Analyzer to increase the throughput for high concurrency installations: ♦ strictMaximumSize. ♦ Data Analyzer Processes To design schemas and reports and use Data Analyzer features more effectively. Any subsequent requests will wait for an object to be returned to the pool.plugins. Otherwise.jboss. If <strictMaximumSize> is set to true.ejb.plugins. Aggregation Data Analyzer can run more efficiently if the data warehouse has a good schema design that takes advantage of aggregate tables to optimize query execution. These parameters are not set by default in Data Analyzer. Ranked Reports Data Analyzer supports two-level ranking.plugins. Data Analyzer performance improves if the data warehouse contains good indexes and is properly tuned. Data Analyzer delegates the ranking task to the database by doing a multi-pass query to first get the ranked items and then running the actual query with ranking filters. if <strictMaximumSize> is set to false.BMPPersistenceManager </persistence-manager> <locking-policy>org.EntityInstanceCache </instance-cache> <persistence-manager>org. If the report has one level of ranking. If you set <strictMaximumSize> to true.QueuedPessimisticEJBLock </locking-policy> <container-cache-conf> <cache-policy>org.jboss.ejb.lock. When the value is set to true. If the ranking is defined on a calculation that is performed in the middle tier. the <strictMaximumSize> parameter enforces a rule that only <MaximumSize> number of objects will be active.LRUEnterpriseContextCachePolicy </cache-policy> <cache-policy-conf> <min-capacity>50</min-capacity> <max-capacity>1000000</max-capacity> <overager-period>300</overager-period> <max-bean-age>600</max-bean-age> <resizer-period>400</resizer-period> <max-cache-miss-period>60</max-cache-miss-period> <min-cache-miss-period>1</min-cache-miss-period> <cache-load-factor>0.plugins.</instance-pool> <instance-cache>org. Data Analyzer Processes 111 .jboss. the number of active objects can exceed the <MaximumSize> if there are requests for more objects. use the following guidelines. then <strictTimeout> is the amount of time that requests will wait for an object to be made available in the pool. only the <MaximumSize> number of objects will be returned to the pool.75</cache-load-factor> </cache-policy-conf> </container-cache-conf> <container-pool-conf> <MaximumSize>100</MaximumSize> </container-pool-conf> <commit-option>A</commit-option> </container-configuration> The following parameter may need tuning: ♦ MaximumSize. then <MaximumSize> is a strict upper limit for the number of objects that will be created. However. Represents the maximum number of objects in the pool. strictTimeout. You can set two other parameters to fine tune the EJB pool.

Data Analyzer runs another SQL query to get the aggregated values for the rows not shown in the report. an interactive chart can use up to 25% less CPU resources than a regular chart. Data Analyzer performs date manipulation on any column with a datatype of Date. For more information about editing your general preferences to enable interactive charts. If a column contains date and time information. then a BigDecimal format for columns in tables with a large volume of data adds unnecessary overhead. If a column contains date information only. If a report includes a column that contains date and time information but the report requires a daily granularity. Date Columns By default. set the Data Source is Timestamp attribute property so that Data Analyzer includes conversion functions in the SQL query for any report the uses the column. set the number of rows to display per page for a report on the Analyze tab. A report with second level ranking. For optimal performance. Step 4 of the Create Report wizard. Use the Data Source is Timestamp property for an attribute to have Data Analyzer include conversion functions in the SQL query. You can control the number of rows displayed on a page in Layout and Setup. JavaScript on the Analyze Tab The Analyze tab in Data Analyzer uses JavaScript for user interaction. such as the top 10 products and the top five customers for each product. not including time. create reports with two levels of ranking based on smaller schemas or on schemas that have good aggregate tables and indexes. Datatype of Table Columns Data Analyzer uses JDBC drivers to connect to the data warehouse. On the Formatting tab. If a high degree of precision is not required. Interactive Charts An interactive chart uses less application server resources than a regular chart. JDBC packages the returned data in a BigDecimal format. Data Analyzer may display messages warning that the JavaScripts on the page are running too slow. clear the Data Source is Timestamp attribute property so that Data Analyzer does not include conversion functions in the SQL query for any report the uses the column. Also. Each cell in a report on the Analyze tab has embedded JavaScript objects to capture various user interactions. based on the column datatype defined in the database. see the Data Analyzer User Guide. which has a high degree of precision. requires a multi-pass SQL query to first get the data to generate the top 10 products and then get the data for each product and corresponding top five customers. However. On a slow workstation with a CPU speed less than 1 GHz.000 cells in a report. On a typical workstation with a CPU speed greater than 2. Set column datatypes to reflect the actual precision required. If a column has a numeric datatype. Make sure that a report displayed in the Analyze tab has a restriction on the number of cells displayed on a page. If you have a data warehouse with a large volume of data.5 GHz.Data Analyzer has to pull all the data before it evaluates the calculation expression and ranks the data and filter. These types of reports consume resources and may slow down other Data Analyzer processes. 112 Chapter 11: Performance Tuning . consider making the report cached so that it can run in the background. Use interactive charts whenever possible to improve performance. If the report is defined to show Total Others at End of Table. interactive charts display at about the same speed as regular charts. conversion functions in a query prevent the use of database indexes and makes the SQL query inefficient. Data Analyzer includes conversion functions in the WHERE clause and SELECT clause to get the proper aggregation and filtering by date only. avoid creating reports with ranking defined on custom attributes or custom metrics. If there are over 5. JDBC uses a different data structure when it returns data. On the machine hosting the application server. the report may take several minutes to display.

user level. However. you have five reports with user-based security and there are 500 security profiles for subscribers to the report. Data Analyzer runs subtasks sequentially. You can increase the value for specific reports that require more data. limit the number of returned rows to a small value. can create problems. By default. For example. If there are a large number of concurrent users on Data Analyzer and each runs multiple reports. Within a task. If ReportA takes six minutes to run. To keep Data Analyzer from consuming more resources than necessary. Data Analyzer generates a subset of the report dataset for each chart.Number of Charts in a Report Data Analyzer generates the report charts after it generates the report table. You can set this parameter at the system level. Scheduler and User-Based Security Data Analyzer supports parallel execution of both time-based and event-based schedulers. Data Analyzer cannot take advantage of parallel scheduler execution and sequentially generates the report for each security profile. Data Analyzer runs only the tasks in an event in parallel mode. and report level. minimize the number of security profiles in Data Analyzer. Data Analyzer saves the dataset returned by the report query in the user session until the user terminates the session. see “Setting Rules for Queries” on page 85. such as every five minutes. at the server level. Frequency of Schedule Runs Setting the report schedules to run very frequently. This situation can drastically affect the performance of Data Analyzer.maxInMemory When a user runs a report. Data Analyzer must pre-fetch all the rows so that the full dataset is available for operations such as ranking or ordering data. Data Analyzer must execute each of the five reports for each of the 500 security profiles. For example. For optimal performance. Data Analyzer keeps two reports in Data Analyzer Processes 113 . Query Governing You can restrict the number of rows returned by an SQL query for a report with the query governing settings in Data Analyzer. use the real-time message stream features available in Data Analyzer. Row Limit for SQL Queries Data Analyzer fetches all the rows returned by an SQL query into the JVM before it displays them on the report. or formatting reports into sections. For more information about query governing. the memory requirements can be considerable. To improve performance. ProviderContext. performing time comparisons. If you require reports to deliver real-time data. Do not use the report schedules to frequently update reports to simulate real-time reports. This means that each chart that Data Analyzer generates for a report has computing overhead associated with it. Since a chart may use only a subset of the report columns and rows as a datapoint. you add ReportA to a schedule that runs every five minutes. it is important to restrict the number of rows returned by the SQL query of a report. such as 1000. Report designers who create a large number of charts to cover all possible user requirements can weaken the performance and scalability of Data Analyzer. To keep Data Analyzer scalable. Data Analyzer starts running ReportA again before the previous run is completed. it may already have fetched hundreds of rows and stored them in the JVM heap. Although Data Analyzer displays only 20 rows in a page. Since generating a report for each security profile is a subtask for each report. consider the overhead cost associated with report charts and create the minimum set of charts required by the end user. You can set parameters in Data Analyzer to restrict the number of rows returned by an SQL query for a report and to manage the amount of memory it uses.

You can edit the providerContext. These parallel threads are default threads spawned by the browser. if the used memory is 1. and the total memory configured for the JVM is 2. To improve Data Analyzer performance. The value must be greater than or equal to 2. Data Analyzer uses the data in the activity log to calculate the Estimated Time to Run the Report for an on-demand 114 Chapter 11: Performance Tuning . by default.000 KB. If the percentage is below the threshold. When there are multiple indicators based on a single report. Include only reports that have small datasets in a workflow. The table indicators use plain HTML instead of DHTML. Data Analyzer has been optimized to handle the way multiple indicators are queued up for loading: ♦ ♦ In a dashboard with indicators based on cached and on-demand reports. Data Analyzer releases the memory after the expiration of session-timeout. you must clear these two logs frequently.properties file to set the maximum percentage of memory that is in use before Data Analyzer stops building report result sets and executing report queries. Set the value as low as possible to conserve memory. To calculate the percentage. For example. which. Typically. Typically. If the percentage is above the threshold. you can set a threshold value between 50% and 99%. divide the used memory by the total memory configured for the JVM. Data Analyzer records every user login in the user log. The default value is 95%. It uses a first in first out (FIFO) algorithm to overwrite reports in memory with more recent reports. Data Analyzer retains report results that are part of a workflow or drill path in memory irrespective of the value set in this property. When a user closes a browser window without logging out. the default value of 2 is sufficient. For more information about managing the activity and user logs. Data Analyzer might run out of memory that results in the users getting a blank page. is 30 minutes.maxInMemory property in DataAnalyzer. ♦ ♦ Purging of Activity Log Data Analyzer logs every activity or event that happens in Data Analyzer in the activity log. You can edit the providerContext. Gauges based on cached reports load the fastest because gauges have only one data value and they are cached in the database along with the report model. If the amount of free memory does not meet a pre-defined percentage. For on-demand reports. Indicators in Dashboard Data Analyzer uses two parallel threads to load indicators in the dashboards. Both for cached and ondemand reports.abortThreshold property in the DataAnalyzer.abortThreshold When a user runs a report that involves calculation or building large result sets. see “Managing System Settings” on page 73. Before Data Analyzer starts calculating the report or building the tabular result set.000 KB. Data Analyzer keeps the datasets for all reports in a workflow in the user session. All indicators on a dashboard based on the same report use the same resultset. Similarly. it checks the amount of available memory. Data Analyzer runs the underlying report once. Data Analyzer loads all indicators based on cached reports before it loads indicators based on on-demand reports. which results in very little overhead for rendering the table indicators on the browser. These logs can grow quickly. the percentage of memory that is in use is 50%. ProviderContext. Note: A user must log out of Data Analyzer to release the user session memory. then Data Analyzer displays an error. Data Analyzer continues with the requested operation. Data Analyzer displays an error and stops processing the report request. Data Analyzer provides an estimate of the length of time a report takes to display. Closing a browser window does not release the memory immediately.properties to set the number of reports that Data Analyzer keeps in memory. Data Analyzer obtains the report model and the datapoint for the gauge at the same time and can immediately create the gauge.the user session at a time.

evictionPeriodMins.maxCapacity=20 dynapool. dynapool. dynapool. The following is a typical configuration: # Datasource definition # dynapool.minCapacity=2 dynapool. modify the connection pool settings in DataAnalyzer. whereas value-based indicators have to perform a linear scan of the rowset to match up the values. Depending on the number of legends in a chart.connectionIdleTimeMins=10 datamart. Regular charts are rendered at server side and use the server CPU resources. Maximum number of connections that the data source pool can grow to. This pool of JDBC connections is different from the pool of connections to the repository defined at the application server level.defaultRowPrefetch=20 The following parameters may need tuning: ♦ dynapool. Use position-based indicators instead of value-based indictors for reports with a volume of more than 2. For more information about the estimation window property. For most cases. Data Analyzer creates a new connection to the data source to calculate a report.evictionPeriodMins=5 dynapool. the Data Analyzer charting engine must perform many complex calculations to fit the legends in the limited space available on the chart. consider displaying the chart without legends to improve Data Analyzer performance. In a high usage environment.maxCapacity. use the following recommendations: ♦ ♦ ♦ For dashboard indicators.window property in DataAnalyzer. Set to 0 to ensure that no connections are maintained in the data source pool. Default is 5 minutes. it might take Data Analyzer from 10% to 50% longer to render a chart with legends. Use aggregate tables for indicators based on ondemand reports on the dashboards. To optimize the database connection pool for a data source. If the value is 0. Typically.report. You can specify the number of days that Data Analyzer uses for the estimate by editing the queryengine. If legends are not essential in a chart. Position-based indicators can use indexes in the java collection for faster access of the database. then the SQL query to calculate the estimated time may take considerable CPU resources because it calculates the estimated time by doing an average of all the entries for a specified number of days. the default value of 30 days is fine. Recommendations for Dashboard Design When you design a dashboard. Number of minutes between eviction runs or clean up operations during which Data Analyzer cleans up failed and idle connections from the connection pool.estimation. Default is 2. If the activity log contains a lot of data.properties. Connection Pool Size for the Data Source Data Analyzer internally maintains a pool of JDBC connections to the data warehouse. Interactive charts are rendered on the browser and require much less server resources. dashboards provide summarized information. use interactive charts on the dashboard. Hence. Minimum number of connections maintained in the data source pool. use indicators based on cached reports instead of on-demand reports.000 rows.properties.minCapacity. Set the value to the total number of concurrent users. Data Analyzer returns an error message to some users. see “Properties in DataAnalyzer.properties” on page 130. the scan can get progressively slower for large datasets. ♦ Chart Legends When Data Analyzer displays charts with legends.waitForConnectionSeconds=1 dynapool. Data Analyzer Processes 115 ♦ ♦ . If you set a value less than the number of concurrent users.

Default is 10. Server Location and Network Latency There are two database components in Data Analyzer: the repository and data warehouse. carefully perform capacity planning and testing before a Data Analyzer deployment. For optimal performance. Make sure that all processes have enough resources to function optimally. network latency between the application server and the data warehouse must also be minimal. ♦ dynapool.waitForConnectionSeconds.evictionPeriodMins is not set. the machine must have enough CPU power and RAM to handle the demands of each of the server processes. Enter a positive value for this parameter. Data Analyzer runs only a few SQL queries against the data warehouse. the requirements for a very powerful machine makes it an expensive solution.You can set the value to half of the value set for the parameter dynapool. If you set the parameter to 0 or a negative value. It also becomes a single point of failure. Data Analyzer runs a large number of SQL queries against the repository to get the metadata before running any report. You can keep the repository and data warehouse on the same database but in separate schemas as long as the machine has enough CPU and memory resources to handle the repository SQL queries and the data warehouse SQL queries. since Data Analyzer runs a large number of them. However. If you set the parameter to 0. However. The choice of architecture depends on the requirements of the organization. Default is 1. As with any major software implementation project. Number of seconds Data Analyzer waits for a connection from the pool before it aborts the operation. Data Analyzer ignores this property if the parameter dynapool. Server Location and CPU Power and RAM If you locate the application server and database server in a single machine. network latency is an issue in a distributed architecture. have the repository database as close as possible to the application server Data Analyzer runs on. dynapool. For optimal performance. An alternative to the single-machine architecture is a distributed system where the servers are located on different machines across a network. The SQL queries that Data Analyzer runs against the repository are not CPU or IO intensive. Typically. the data warehouse requires more CPU power than the repository database. Although a single-machine architecture means that there is no network latency. these servers must have enough CPU power and RAM. ♦ Server Location Data Analyzer runs on an application server and reads data from a database server. and does not allow a connection to remain idle for too long. Data Analyzer sets the parameter to the default value.connectionIdleTimeMins so that Data Analyzer performs the eviction run. Number of minutes that a connection may remain idle. Since the queries return many rows. Note: Data Analyzer connects to only one repository database. it can connect to more than one data warehouse. However. The SQL queries that Data Analyzer runs against the data warehouse return many rows and are CPU and IO intensive. frees the connections for report calculations. network latency between the application server and the repository database must be minimal. This type of distributed architecture can be more economical because it can leverage existing infrastructure.connectionIdleTimeMins. 116 Chapter 11: Performance Tuning . There should also be minimal network latency between these servers. Data Analyzer does not wait and aborts the operation.

118 Overview You can customize the Data Analyzer user interface so that it meets the requirements for web applications in your organization.properties file to display or hide the Data Analyzer header or navigation bar. For more information about the Data Analyzer URL API. 118 Setting the UI Configuration Properties. such as dashboard.CHAPTER 12 Customizing the Data Analyzer Interface This chapter includes the following topics: ♦ ♦ ♦ ♦ ♦ Overview. 118 Setting Up Color Schemes and Logos. Using the Data Analyzer URL API You can use the URL interface provided with the Data Analyzer API to provide links in a web application or portal to specific pages in Data Analyzer. 117 Using the Data Analyzer API Single Sign-On. Set the user interface (UI) configuration properties in the DataAnalyzer. Set up custom color schemes and logos on the Data Analyzer Administration tab. You can use the following techniques to customize Data Analyzer: ♦ ♦ ♦ ♦ Use the URL API to display Data Analyzer web pages on a portal. 117 . 117 Using the Data Analyzer URL API. or tab pages. Use the Data Analyzer API single sign on (SSO) scheme to access Data Analyzer web pages without a user login. The URL consists of the Data Analyzer location and parameters that determine the content and interface for the Data Analyzer page. Data Analyzer provides several ways to allow you to modify the look and feel of Data Analyzer. report. see the Data Analyzer SDK Guide.

You can use the default Informatica color scheme and the sample color scheme named Betton Books as a starting point for a custom color scheme.default.ShowHeader=false 118 Chapter 12: Customizing the Data Analyzer Interface . when a user logs in to Data Analyzer through the Login page. Setting Up Color Schemes and Logos Data Analyzer provides two color schemes for the Data Analyzer interface. if you display Data Analyzer web pages in another web application or portal.ShowNav=true The properties determine what displays in the header section of the Data Analyzer user interface which includes the logo. add the following property: uiconfig.ShowHeader=true uiconfig. and navigation bar display on all the Data Analyzer pages. see the Data Analyzer SDK Guide. The UI configuration include the following properties: uiconfig. You can configure Data Analyzer to accept the portal authentication and bypass the Data Analyzer login page. the Data Analyzer login appears even if you have already logged in to the portal where the Data Analyzer pages are displayed. buttons. You must enter a user name and password. and logos to match the standard color scheme for the web applications in your organization. To hide the navigation bar or the header section on the Data Analyzer pages. Setting the UI Configuration Properties In DataAnalyzer. To hide the whole header section.<ConfigurationName>. Ordinarily. logout and help links. see “Managing Color Schemes and Logos” on page 74.<ConfigurationName>. you can set up an SSO mechanism that allows you to log in once and be authenticated in all subsequent web applications that you access. you can add a UI configuration named default to DataAnalyzer. the logout and help links.properties and set the properties to false. the login page appears.Using the Data Analyzer API Single Sign-On When you access Data Analyzer.properties. To avoid multiple logins. the logo. You can also create color schemes and use custom graphics. For more information about the Data Analyzer API SSO. For more information. The Data Analyzer API provides an SSO mechanism that you can use when you display Data Analyzer pages in another web application or portal. and the navigation bar: Navigation Bar Header Section Default UI Configuration By default. you can define a user interface configuration that determines how Data Analyzer handles specific sections of the user interface.

If you want to change the default configuration settings. UI Configuration Parameter in Data Analyzer URL If you use the URL API to display Data Analyzer pages on another web application or a portal. The configuration name can be any length and is case sensitive. see “Configuration Files” on page 129. to display the Data Analyzer administration page on a portal without the navigation bar. If you access a Data Analyzer page with a specific configuration through the URL API and the session expires. It cannot include special characters. the Login page appears. The header section of the Data Analyzer page appears on the portal according to the setting in the configuration. Add them only if you want to modify the default configuration settings or create new UI configurations. Data Analyzer displays the Data Analyzer pages based on the default configuration. complete the following steps: 1. Configuration Settings Use the following guidelines when you set up a configuration in DataAnalyzer. you can add a configuration to DataAnalyzer.jsp?<UICONFIG>=Fred For more information about the Data Analyzer URL API. For example. For more information about modifying the settings in DataAnalyzer. Setting the UI Configuration Properties 119 . see the Data Analyzer SDK Guide. Set the default configuration to the same values as your customized configuration.properties and include the configuration name in the URL. It can include only alphanumeric characters. specifying a configuration name: uiconfig.Fred.ShowNav=false 2.default.properties.ShowHeader=true uiconfig. To avoid this.properties: ♦ ♦ ♦ The default configuration properties are not required in DataAnalyzer.ShowNav=false Tip: DataAnalyzer. Customize the Data Analyzer login page to use your customized configuration after user login.properties.properties includes examples of the properties for the default UI configuration. not the configuration passed through the URL. Setting the ShowHeader property to false implicitly sets the ShowNav property to false. After you login. Include the parameter <UICONFIG> and the configuration name in the URL when you call the Data Analyzer Administration page from the portal: http://HostName:PortNumber/InstanceName/jsp/api/ShowAdministration. add the following property: uiconfig. The default settings determine what Data Analyzer displays after the Login page. complete one of the following tasks: ♦ ♦ ♦ Change the values of the default configuration instead of adding a new configuration.Fred.properties. Add the following properties to DataAnalyzer.To hide only the navigation bar. uncomment the default properties and update the values of the properties.

The following examples show what appears on the Data Analyzer header when the UI configuration properties are set to different values: ♦ ShowHeader=true and ShowNav=true (default setting) ♦ ShowHeader=true and ShowNav=false ♦ ShowHeader=false and ShowNav=false Note: Data Analyzer stores DataAnalyzer.properties in the Data Analyzer EAR file.properties from the Data Analyzer EAR file before you can modify the UI configuration properties. You must use the EAR Repackager utility to extract DataAnalyzer. 120 Chapter 12: Customizing the Data Analyzer Interface .

121 HTML Hexadecimal Color Codes You can create new color schemes for Data Analyzer by entering valid HTML hexadecimal color codes into the appropriate fields on the Color Scheme page. For more information about creating a color scheme. Table A-1 lists the colors and hexadecimal color codes you can use when creating color schemes for Data Analyzer: Table A-1.APPENDIX A Hexadecimal Color Codes This appendix includes the following topic: ♦ HTML Hexadecimal Color Codes. see “Managing Color Schemes and Logos” on page 74. For example. HTML Color Codes for Color Schemes Color Name alice blue antique white antique white1 antique white2 antique white3 antique white4 aquamarine aquamarine1 aquamarine2 aquamarine3 aquamarine4 azure azure1 azure2 azure3 Color Code F0F8FF FAEBD7 FFEFDB EEDFCC CDC0B0 8B8378 7FFFD4 7FFFD4 76EEC6 66CDAA 458B74 F0FFFF F0FFFF E0EEEE C1CDCD Color Name blue blue violet blue1 blue2 blue3 blue4 brown brown1 brown2 brown3 brown4 burlywood burlywood1 burlywood2 burlywood3 Color Code 0000FF 8A2BE2 0000FF 0000EE 0000CD 00008B A52A2A FF4040 EE3B3B CD3333 8B2323 DEB887 FFD39B EEC591 CDAA7D 121 . you can alter the colors in Data Analyzer to match your corporate color scheme.

HTML Color Codes for Color Schemes Color Name azure4 beige bisque bisque1 bisque2 bisque3 bisque4 black blanched almond chartreuse3 chartreuse4 chocolate chocolate1 chocolate2 chocolate3 chocolate4 coral coral1 coral2 coral3 coral4 cornflower blue cornsilk cornsilk1 cornsilk2 cornsilk3 cornsilk4 cyan cyan1 cyan2 cyan3 cyan4 dark blue dark cyan dark goldenrod dark goldenrod1 dark goldenrod2 dark goldenrod4 Color Code 838B8B F5F5DC FFE4C4 FFE4C4 EED5B7 CDB79E 8B7D6B 000000 FFEBCD 66CD00 458B00 D2691E FF7F24 EE7621 CD661D 8B4513 FF7F50 FF7256 EE6A50 CD5B45 8B3E2F 6495ED FFF8DC FFF8DC EEE8CD CDC8B1 8B8878 00FFFF 00FFFF 00EEEE 00CDCD 008B8B 00008B 008B8B B8860B FFB90F EEAD0E 8B6508 Color Name burlywood4 cadet blue cadet blue1 cadet blue2 cadet blue3 cadet blue4 chartreuse chartreuse1 chartreuse2 dark khaki dark magenta dark olive green dark orange dark orange1 dark orange2 dark orange3 dark orange4 dark orchid dark orchid1 dark orchid2 dark orchid3 dark orchid4 dark red dark salmon dark sea green dark slate blue dark slate gray dark turquoise dark violet dark goldenrod3 dark olive green1 dark olive green2 dark olive green3 dark olive green4 dark sea green1 dark sea green2 dark sea green3 dark sea green4 Color Code 8B7355 5F9EA0 98F5FF 8EE5EE 7AC5CD 53868B 7FFF00 7FFF00 76EE00 BDB76B 8B008B 556B2F FF8C00 FF7F00 EE7600 CD6600 8B4500 9932CC BF3EFF B23AEE 9A32CD 68228B 8B0000 E9967A 8FBC8F 483D8B 2F4F4F 00CED1 9400D3 CD950C CAFF70 BCEE68 A2CD5A 6E8B3D C1FFC1 B4EEB4 9BCD9B 698B69 122 Appendix A: Hexadecimal Color Codes .Table A-1.

Table A-1. HTML Color Codes for Color Schemes
Color Name dark gray dark green dark slate gray3 dark slate gray4 deep pink deep pink1 deep pink2 deep pink3 deep pink4 dark slate gray3 deep sky blue deep sky blue1 deep sky blue2 deep sky blue3 deep sky blue4 dim gray dodger blue dodger blue1 dodger blue2 dodger blue3 dodger blue4 firebrick firebrick1 firebrick2 firebrick3 firebrick4 floral white forest green gainsboro ghostwhite gold gold1 gold2 gray22 gray23 gray24 gray25 gray26 Color Code A9A9A9 006400 79CDCD 528B8B FF1493 FF1493 EE1289 CD1076 8B0A50 79CDCD 00BFFF 00BFFF 00B2EE 009ACD 00688B 696969 1E90FF 1E90FF 1C86EE 1874CD 104E8B B22222 FF3030 EE2C2C CD2626 8B1A1A FFFAF0 228B22 DCDCDC F8F8FF FFD700 FFD700 EEC900 383838 3B3B3B 3D3D3D 404040 424242 Color Name dark slate gray1 dark slate gray2 gold3 deep sky blue deep sky blue1 deep sky blue2 deep sky blue3 deep sky blue4 dim gray dodger blue gold4 goldenrod goldenrod1 goldenrod2 goldenrod3 goldenrod4 gray gray0 gray1 gray10 gray100 gray11 gray12 gray13 gray14 gray15 gray16 gray17 gray18 gray19 gray2 gray20 gray21 gray50 gray51 gray52 gray53 gray54 Color Code 97FFFF 8DEEEE CDAD00 00BFFF 00BFFF 00B2EE 009ACD 00688B 696969 1E90FF 8B7500 DAA520 FFC125 EEB422 CD9B1D 8B6914 BEBEBE 000000 030303 1A1A1A FFFFFF 1C1C1C 1F1F1F 212121 242424 262626 292929 2B2B2B 2E2E2E 303030 050505 333333 363636 7F7F7F 828282 858585 878787 8A8A8A

HTML Hexadecimal Color Codes

123

Table A-1. HTML Color Codes for Color Schemes
Color Name gray27 gray28 gray29 gray3 gray30 gray31 gray32 gray33 gray34 gray35 gray36 gray37 gray38 gray39 gray4 gray40 gray41 gray42 gray43 gray44 gray45 gray46 gray47 gray48 gray49 gray5 gray79 gray8 gray80 gray81 gray82 gray83 gray84 gray85 gray86 gray87 gray88 gray89 Color Code 454545 474747 4A4A4A 080808 4D4D4D 4F4F4F 525252 545454 575757 595959 5C5C5C 5E5E5E 616161 636363 0A0A0A 666666 696969 6B6B6B 6E6E6E 707070 737373 757575 787878 7A7A7A 7D7D7D 0D0D0D C9C9C9 141414 CCCCCC CFCFCF D1D1D1 D4D4D4 D6D6D6 D9D9D9 DBDBDB DEDEDE E0E0E0 E3E3E3 Color Name gray55 gray56 gray57 gray58 gray59 gray6 gray60 gray61 gray62 gray63 gray64 gray65 gray66 gray67 gray68 gray69 gray7 gray70 gray71 gray72 gray73 gray74 gray75 gray76 gray77 gray78 honeydew1 honeydew2 honeydew3 honeydew4 hot pink hot pink3 hot pink4 hot pink1 indian red indian red1 indian red2 indian red3 Color Code 8C8C8C 8F8F8F 919191 949494 969696 0F0F0F 999999 9C9C9C 9E9E9E A1A1A1 A3A3A3 A6A6A6 A8A8A8 ABABAB ADADAD B0B0B0 121212 B3B3B3 B5B5B5 B8B8B8 BABABA BDBDBD BFBFBF C2C2C2 C4C4C4 C7C7C7 F0FFF0 E0EEE0 C1CDC1 838B83 FF69B4 CD6090 8B3A62 FF6EB4 CD5C5C FF6A6A EE6363 CD5555

124

Appendix A: Hexadecimal Color Codes

Table A-1. HTML Color Codes for Color Schemes
Color Name gray9 gray90 gray91 gray92 gray93 gray94 gray95 gray96 gray97 gray98 gray99 green green yellow green1 green2 green3 green4 hot pink 2 honeydew lemon chiffon 2 lemon chiffon 3 lemon chiffon1 lemon chiffon4 light blue light blue2 light blue3 light coral light cyan light goldenrod light goldenrod yellow light goldenrod1 light goldenrod2 light goldenrod3 light goldenrod4 light gray light green light pink light salmon Color Code 171717 E5E5E5 E8E8E8 EBEBEB EDEDED F0F0F0 F2F2F2 F5F5F5 F7F7F7 FAFAFA FCFCFC 00FF00 ADFF2F 00FF00 00EE00 00CD00 008B00 EE6AA7 F0FFF0 EEE9BF CDC9A5 FFFACD 8B8970 ADD8E6 B2DFEE 9AC0CD F08080 E0FFFF EEDD82 FAFAD2 FFEC8B EEDC82 CDBE70 8B814C D3D3D3 90EE90 FFB6C1 FFA07A Color Name indian red4 ivory ivory1 ivory2 ivory3 ivory4 khaki khaki1 khaki2 khaki3 khaki4 lavender lavender blush lavender blush1 lavender blush2 lavender blush3 lavender blush4 lawn green lemon chiffon light yellow2 light yellow3 light yellow4 light blue1 light blue4 light cyan1 light cyan2 light cyan3 light cyan4 light pink1 light pink2 light pink3 light pink4 light sky blue1 light sky blue2 light sky blue3 light skyblue4 light steel blue1 light steel blue2 Color Code 8B3A3A FFFFF0 FFFFF0 EEEEE0 CDCDC1 8B8B83 F0E68C FFF68F EEE685 CDC673 8B864E E6E6FA FFF0F5 FFF0F5 EEE0E5 CDC1C5 8B8386 7CFC00 FFFACD EEEED1 CDCDB4 8B8B7A BFEFFF 68838B E0FFFF D1EEEE B4CDCD 7A8B8B FFAEB9 EEA2AD CD8C95 8B5F65 B0E2FF A4D3EE 8DB6CD 607B8B CAE1FF BCD2EE

HTML Hexadecimal Color Codes

125

HTML Color Codes for Color Schemes Color Name light salmon1 light salmon2 light salmon3 light salmon4 light sea green light sky blue light slate blue light slate gray light steel blue light steel blue4 light yellow light yellow1 maroon4 medium slate blue medium aquamarine medium blue medium orchid medium orchid1 medium orchid2 medium orchid3 medium orchid4 medium purple medium purple1 medium purple2 medium purple3 medium purple4 medium sea green medium spring green medium turquoise medium violet red midnight blue mint cream misty rose misty rose1 misty rose2 misty rose3 misty rose4 moccasin Color Code FFA07A EE9572 CD8162 8B5742 20B2AA 87CEFA 8470FF 708090 B0C4DE 6E7B8B FFFFE0 FFFFE0 8B1C62 7B68EE 66CDAA 0000CD BA55D3 E066FF D15FEE B452CD 7A378B 9370DB AB82FF 9F79EE 8968CD 5D478B 3CB371 00FA9A 48D1CC C71585 191970 F5FFFA FFE4E1 FFE4E1 EED5D2 CDB7B5 8B7D7B FFE4B5 Color Name light steel blue3 lime green linen magenta magenta1 magenta2 magenta3 magenta4 maroon maroon1 maroon2 maroon3 navy old lace olive drab olive drab1 olive drab2 olive drab3 olive drab4 orange orange red orange red1 orange red2 orange red3 orange red4 orange1 orange2 orange3 orange4 orchid orchid1 orchid2 orchid3 orchid4 pale goldenrod pale green pale green1 pale green2 Color Code A2B5CD 32CD32 FAF0E6 FF00FF FF00FF EE00EE CD00CD 8B008B B03060 FF34B3 EE30A7 CD2990 000080 FDF5E6 6B8E23 C0FF3E B3EE3A 9ACD32 698B22 FFA500 FF4500 FF4500 EE4000 CD3700 8B2500 FFA500 EE9A00 CD8500 8B5A00 DA70D6 FF83FA EE7AE9 CD69C9 8B4789 EEE8AA 98FB98 9AFF9A 90EE90 126 Appendix A: Hexadecimal Color Codes .Table A-1.

Table A-1. HTML Color Codes for Color Schemes Color Name navajo white navajo white1 navajo white2 navajo white3 navajo white4 pale turquoise3 pale turquoise4 pale violet red pale violet red 2 pale violet red 3 pale violet red1 pale violet red4 papaya whip peach puff peach puff1 peach puff2 peach puff3 peach puff4 peru pink pink1 pink2 pink3 pink4 plum plum1 plum2 plum3 plum4 powder blue purple purple1 purple2 purple3 purple4 red sienna sienna1 Color Code FFDEAD FFDEAD EECFA1 CDB38B 8B795E 96CDCD 668B8B DB7093 EE799F CD6889 FF82AB 8B475D FFEFD5 FFDAB9 FFDAB9 EECBAD CDAF95 8B7765 CD853F FFC0CB FFB5C5 EEA9B8 CD919E 8B636C DDA0DD FFBBFF EEAEEE CD96CD 8B668B B0E0E6 A020F0 9B30FF 912CEE 7D26CD 551A8B FF0000 A0522D FF8247 Color Name pale green3 pale green4 pale turquoise pale turquoise1 pale turquoise2 red1 red2 red3 red4 rosy brown rosybrown1 rosybrown2 rosybrown3 rosybrown4 royal blue royal blue1 royal blue2 royal blue3 royal blue4 saddle brown salmon salmon1 salmon2 salmon3 salmon4 sandy brown sea green seagreen1 seagreen2 seagreen3 seagreen4 seashell seashell1 seashell2 seashell3 seashell4 steel blue2 steel blue3 Color Code 7CCD7C 548B54 AFEEEE BBFFFF AEEEEE FF0000 EE0000 CD0000 8B0000 BC8F8F FFC1C1 EEB4B4 CD9B9B 8B6969 4169E1 4876FF 436EEE 3A5FCD 27408B 8B4513 FA8072 FF8C69 EE8262 CD7054 8B4C39 F4A460 2E8B57 54FF9F 4EEE94 43CD80 2E8B57 FFF5EE FFF5EE EEE5DE CDC5BF 8B8682 5CACEE 4F94CD HTML Hexadecimal Color Codes 127 .

HTML Color Codes for Color Schemes Color Name sienna2 sienna3 sienna4 sky blue sky blue1 sky blue2 sky blue3 sky blue4 slate blue slate blue1 slate blue2 slate blue3 slate blue4 slate gray slate gray1 slate gray2 slate gray3 slategray4 snow1 snow2 snow3 snow4 spring green spring green1 spring green2 spring green3 spring green4 steel blue steel blue1 wheat2 wheat3 wheat4 white white smoke yellow Color Code EE7942 CD6839 B47268 87CEEB 87CEFF 7EC0EE 6CA6CD 4A708B 6A5ACD 836FFF 7A67EE 6959CD 473C8B 778899 C6E2FF B9D3EE 9FB6CD 6C7B8B FFFAFA EEE9E9 CDC9C9 8B8989 00FF7F 00FF7F 00EE76 00CD66 008B45 4682B4 63B8FF EED8AE CDBA96 8B7E66 FFFFFF F5F5F5 FFFF00 Color Name steel blue4 tan tan1 tan2 tan3 tan4 thistle thistle1 thistle2 thistle3 thistle4 tomato tomato1 tomato2 tomato3 tomato4 turquoise turquoise1 turquoise2 turquoise3 turquoise4 violet violet red violet red 1 violet red 2 violet red3 violet red4 wheat wheat1 yellow green yellow1 yellow2 yellow3 yellow4 Color Code 36648B D2B48C FFA54F EE9A49 CD853F 8B5A2B D8BFD8 FFE1FF EED2EE CDB5CD 8B7B8B FF6347 FF6347 EE5C42 CD4F39 8B3626 40E0D0 00F5FF 00E5EE 00C5CD 00868B EE82EE D02090 FF3E96 EE3A8C CD3278 8B2252 F5DEB3 FFE7BA 9ACD32 FFFF00 EEEE00 CDCD00 8B8B00 128 Appendix A: Hexadecimal Color Codes .Table A-1.

xml. 129 Properties in DataAnalyzer. They are stored in the Data Analyzer EAR directory. Contains additional configuration settings for an instance of Data Analyzer. you can modify the Data Analyzer configuration files.xml. Although infacache-service. The configuration files define the appearance and operational parameters of Data Analyzer.xml.xml web. you only need to modify specific settings.xml contains many settings. The following configuration files that contain the settings for an instance of Data Analyzer are stored in its EAR file: ♦ ♦ ♦ DataAnalyzer.xml. Contains the global cache configuration settings for Data Analyzer.properties.properties infa-cache-service. 141 Overview To customize Data Analyzer for your organization.APPENDIX B Configuration Files This appendix includes the following topics: ♦ ♦ ♦ ♦ ♦ Overview. you only need to modify specific settings.xml contains many settings. Contains the configuration settings for an instance of Data Analyzer. ♦ Modifying the Configuration Files Each instance of Data Analyzer has an associated enterprise archive (EAR) file. You can modify the following configuration files: ♦ ♦ DataAnalyzer.xml 129 . 137 Properties in web. infa-cache-service. 129 Modifying the Configuration Files. Although web. They are stored in the Data Analyzer EAR directory. 130 Properties in infa-cache-service. They are stored in the Data Analyzer EAR directory.properties. web.

− − securityadapter.syncOnSystemStart 130 Appendix B: Configuration Files .minCapacity dynapool. Data Analyzer provides a synchronization scheduler that you can customize to set the schedule for these updates based on the requirements of your organization. In the following groups of properties.connectionIdleTimeMins datamart. If you use LDAP authentication. Several properties in DataAnalyzer.maxCapacity dynapool. see “Connection Pool Size for the Data Source” on page 115. You can modify DataAnalyzer.properties The DataAnalyzer. Data Analyzer periodically updates the list of users and groups in the repository with the list of users and groups in the LDAP directory service.properties file contains the configuration settings for an instance of Data Analyzer. You must customize some properties in DataAnalyzer.To change the settings in the configuration files stored in the Data Analyzer EAR file. 3. complete the following steps: 1.waitForConnectionSeconds dynapool. open the configuration file you want to modify and search for the setting you want to customize. 2. you may need to modify more than one property to effectively customize Data Analyzer operations: ♦ Dynamic Data Source Pool Properties.defaultRowPrefetch For more information. ♦ Security Adapter Properties. you can modify the following properties.properties control the processes within the connection pool. modify the following properties: − − − − − − dynapool.properties to customize the operation of an instance of Data Analyzer. Change the settings and save the configuration file. To optimize the database connection pool for a data source.frequency securityadapter.evictionPeriodMins dynapool.properties together to achieve a specific result. Properties in DataAnalyzer. Data Analyzer internally maintains a pool of JDBC connections to the data source. To customize the synchronization scheduler. With a text editor. Restart Data Analyzer.

Default is Helvetica. Compatibility level of the API.1 API.ConfigurationName. However. and enabled interactive charts. . The font must exist on the machine hosting Data Analyzer.properties Property alert. If you use an SMTP mail server.The machine where the repository database resides performs fast enough that enabling global caching does not provide a performance gain. Default is true. you must enter an email address that includes a domain. Font to use in all charts generated by this instance of Data Analyzer.NoOfDaysToExpire Chart.level Cache.properties 131 .ConfigurationName. Default is 7. Determines whether global caching is enabled for the repository.Report.Subscription. Number of days before a subscription for cached reports expires.compatibility. Properties in DataAnalyzer. see “Properties in infa-cache-service.Fontname Properties in DataAnalyzer. For more information about configuring global caching. You can modify several properties in this file to customize how the global cache works.GlobalCaching Cache. If set to false.properties labeled For Data Analyzer system use only.♦ UI Configuration Properties. Set it to 40 to force the current API to behave in the same way as the Data Analyzer 4.com. This set of properties determine the look and feel of the Data Analyzer user interface. the font must also exist on the workstation that accesses Data Analyzer. Default is alert@informatica. Table B-1 describes the properties in the DataAnalyzer. infa-cache-service.properties file: Table B-1. Data Analyzer retrieves objects from the repository each time a user accesses them. For more information about editing your general preferences to enable interactive charts. see the Data Analyzer User Guide. you can modify the following properties: − − uiconfig. When a user accesses an object that exists in the cache.xml” on page 137. To customize the navigation and header display of Data Analyzer. api. Data Analyzer creates a cache in memory for repository objects accessed by Data Analyzer users. Set it to blank to use the current API. Together they define a single user interface configuration.0 and 4. Supported values are 40 or blank. the font does not have to exist on the workstation. Data Analyzer retrieves it from the cache instead of accessing the repository.ShowNav Note: Do not modify the properties in the section of DataAnalyzer. If set to true. When global caching is enabled. If you are using the Internet Explorer browser. you need to enter a valid email address for your organization. You might want to disable global caching for the following reasons: .xml determines how the global cache is configured. have installed Adobe SVG Viewer. Leaving the default value does not affect alert functionality.ShowHeader uiconfig. If you are using the Mozilla Firefox browser.fromaddress Description From address used for alerts sent by Data Analyzer. Set to true to increase Data Analyzer performance.The machine running Data Analyzer has insufficient memory for the global cache.

Minimum size (in bytes) for a response to trigger compression. Using this property may result in marginally better performance than using compressionFilter. Data Analyzer compresses only the MIME types listed in compressionFilter.compressableMimeTypes after verifying browser support.compressableMimeTypes compressionFilter. but will not use a font size smaller than the value of this property.Minfontsize compression. Enter a comma-separated list of MIME types. These MIME types may work with compression regardless of whether the browser supports compression or if an intervening proxy would otherwise break compression. no MIME types are listed. if Data Analyzer compresses a MIME type not supported by the browser. Enter a commaseparated list of MIME types. Default is 7. If Data Analyzer users select more data points than the value of this property. Maximum number of rows that Data Analyzer fetches in a report query.Table B-1. Data Analyzer does not compress dynamic content of the unsupported MIME type. Default is 30.properties Property Chart. MIME types for dynamic content that Data Analyzer compresses. By default. Data Analyzer determines the actual font size. Data Analyzer compresses dynamic content of the following MIME types: text/html.MaximumNumberofContainers datamart. the browser might display an error.compressThreshold CustomLayout. The value must be smaller than the value of Chart. Default is 20. Some MIME types are handled by plug-ins that decompress natively. Default is 1000. If the browser does not support compressed files of a MIME type. Typically. text/javascript. Data Analyzer determines the actual font size. but will not use a font size larger than the value of this property. Maximum number of data points to plot in all charts. application/x-javascript. Minimum font size to use on the chart axis labels and legend. Default is 512. MIME types for dynamic content that Data Analyzer always compresses.defaultRowPrefetch 132 Appendix B: Configuration Files .Fontsize Description Maximum font size to use on the chart axis labels and legend. Default is 10.Fontsize. Maximum number of containers allowed in custom layouts for dashboards. an error message appears. Data Analyzer compresses responses if the response size is larger than this number and if it has a compressible MIME type.compressableMimeTypes. By default. the default is sufficient for most organizations. Chart. Properties in DataAnalyzer.MaxDataPoints Chart. However.alwaysCompressMimeTypes compressionFilter. without verifying that the browser can support compressed files of this MIME type.

Dirty reads cannot occur.SERIALIZABLE. Dirty reads and non-repeatable reads cannot occur. Properties in DataAnalyzer.maxCapacity dynapool. If set to false. Nonrepeatable reads and phantom reads can occur.ias_demo=READ_UNC OMMITTED . Minimum number of initial connections in the data source pool. Transactions are not supported.0. Default is 2.allowShrinking dynapool.NONE.Table B-1. Dirty reads.initialCapacity dynapool. Dirty reads. DataSourceName Description Transaction isolation level for each data source used in your Data Analyzer instance. If no property is set for a data source. For more information about CLOB support. For example.x and previous releases and does not support AND/OR conditions in data restriction filters.READ_UNCOMMITTED. Maximum number of connections that the data source pool may grow to. If set to true. Data Analyzer uses the data restriction merging behaviors in Data Analyzer 4. datatype.datamart. Default is 20. Set the value to 25% of the maximum concurrent users. .ias_test=REPEATABLE _READ DataRestriction.READ_COMMITTED. Increasing this setting can slowData Analyzer performance. Set the value to the total number of concurrent users. The value cannot exceed dynapool. you have a data source named ias_demo that you want to set to READ_UNCOMMITTED and another data source named ias_test that you want to set to REPEATABLE_READ (assuming that the databases these data sources point to support the respective transaction levels). Add a property for each data source and then enter the appropriate value for that data source. Phantom reads can occur. Number of connections that can be added at one time.poolNamePrefix Properties in DataAnalyzer. Data Analyzer uses the data restriction merging behavior provided in Data Analyzer 5. Default is 2. and phantom reads can occur. . Default is true.transactionIsolationLevel.1 and supports AND/OR conditions in data restriction filters. non-repeatable reads. String to use as a prefix for the dynamic JDBC pool name. The value must be greater than zero. Default is false.properties Property datamart.OldBehavior Provided for backward compatibility.REPEATABLE_READ. Default is IAS_.properties 133 . . Data Analyzer uses the default transaction level of the database. Determines whether the pool can shrink when connections are not in use.transactionIsolationLevel. Supported values are: .CLOB. Default is 1000.capacityIncrement dynapool. non-repeatable reads. and phantom reads cannot occur.transactionIsolationLevel. . Add the following entries: . see the Data Analyzer Schema Designer Guide.datamart. Determines the maximum number of characters in a CLOB attribute that Data Analyzer displays in a report cell.datalength dynapool.maxCapacity.

Set to false if you do not want the Data Analyzer report to group the data based on the row attributes. the number of connections in the pool reverts to the value of its initialCapacity parameter if the allowShrinking parameter is true.waitSec GroupBySuppression. Maximum number of seconds a client waits to grab a connection from the pool if none is readily available before giving a timeout error. Set to true to append new messages.shrinkPeriodMins dynapool. Set to true to group values by the row attributes. To import a large XML file. If the data source stores a dataset in a single row in a table. Default is 300 seconds (5 minutes).Table B-1. By default. After this period. Data Analyzer should not perform the check too frequently because it locks up the connection pool and may prevent other clients from grabbing connections from the pool. Default is true. the value of this property does not affect how the report displays.url host.url import. Determines whether Data Analyzer groups values by row attributes in cross tabular report tables for reports with a suppressed GROUP BY clause when the data source stores a dataset in more than one row in a table. Number of minutes Data Analyzer allows an idle connection to be in the pool. the installation process installs online help files on the same machine as Data Analyzer and sets the value of this property. Default is 3600 seconds (1 hour). the Data Analyzer installation sets the value of this property in the following format: http://Hostname:PortNumber/InstanceName/ Number of seconds after which the import transaction times out. see the Data Analyzer User Guide. Determines whether to append or overwrite new log information to the JDBC log file. Default is true. you might need to increase this value.files.seconds Indicator. Frequency in seconds that Data Analyzer refreshes indicators with animation. Properties in DataAnalyzer. URL for the Data Analyzer instance. dynapool. For more information.timeout.refreshTestMinutes Description Frequency in minutes at which Data Analyzer performs a health check on the idle connections in the pool.log.transaction.properties Property dynapool. URL for the location of Data Analyzer online help files.waitForConnection dynapool.append 134 Appendix B: Configuration Files .pollingIntervalSeconds jdbc. Set to false to overwrite existing information. Default is 5. Default is true. Default is 60. Default is 1. By default.GroupOnAttributePair help. Determines whether Data Analyzer waits for a database connection if none are available in the connection pool.

Table B-1. defaults to 1000. If the percentage is below the threshold.log If you do not specify a path. Displaying a number larger than the default value may cause the browser to stop responding. To specify a path. Default is 1000.log in a directory called Log_Files in the D: drive.maxRowsToDisplay Maps.window Properties in DataAnalyzer. to set the log file to myjdbc. The percentage is calculated by dividing the used memory by the total memory configured for the JVM. Number of days used to estimate the query execution time for a particular report. Number of reports that Data Analyzer keeps in memory for a user session. For example. Defines the maximum percentage of memory that is in use before Data Analyzer stops building report result sets and running report queries.HeaderFooter. Properties in DataAnalyzer. Data Analyzer creates the JDBC log file in the following default directory: <PowerCenter_install folder>/server/tomcat/jboss/bin/ Default is iasJDBC. Set to true to allow Data Analyzer to shrink the font size of long headers and footers to fit the configured space. Default is true. Set to false to use the configured font size and allow Data Analyzer to display only the text that fits in the header or footer. The directory must be located on the machine where Data Analyzer is installed.maxRowsToDisplay Maximum number of rows to display in the activity log.properties Property jdbc. Data Analyzer displays an error and notifies the user about the low memory condition. Data Analyzer estimates the execution time for a report by averaging all execution times for that report during this estimation window. If set to zero. If not specified.activity. Data Analyzer does not consider the value set for this property while retaining results of the reports that are part of workflow or drill path. Default is 30. defaults to 1000. Default is 95. Default is 1000. Data Analyzer displays an unlimited number of rows. Displaying a number larger than the default value may cause the browser to stop responding.log. Data Analyzer continues with the requested operation. The default location is in the following directory: <PCAEInstallationDirectory>/DataAnalyzer/ maps logging.log.abortThresHold queryengine. If the percentage is above the threshold.properties 135 .estimation. Data Analyzer does not retain report results when you set the property value below 2.ShrinkToWidth Determines how Data Analyzer handles header and footer text in reports saved to PDF. logging.log.file Description Name of the JDBC log file. Data Analyzer displays an unlimited number of rows. use the forward slash (/) or two backslashes (\\) as the file separator.file=d:/Log_Files/myjdbc. If not specified.maxInMemory providerContext.Directory PDF. Maximum number of rows to display in the user log. set the value of the property to include the path and file name: jdbc. If set to zero. The default value is 2. Data Analyzer does not support a single backslash as a file separator. see “Configuring Report Headers and Footers” on page 88.user. For more information. Directory where the XML files that represent maps for the Data Analyzer geographic charts are located. providerContext.

This property specifies the interval between the end of the last synchronization and the start of the next synchronization. Determines the number of minutes between synchronization of the Data Analyzer user list. Data Analyzer does not synchronize the user list at startup.frequency securityadapter. Data Analyzer rounds the value up to the next value divisible by 5.compress 136 Appendix B: Configuration Files . Default is true.userReportDisplayMode securityadapter.properties and set the value of the batch size. Data Analyzer disables all user list synchronization. If the value is not an increment of 5.maxRowsPerTable report. Users can change this default report view by editing their Report Preferences on the Manage Account tab. Determines whether Data Analyzer displays the Summary section in a sectional report table when you email a report from the Find tab or when you use the Data Analyzer API to generate a report. If the property is not set. Set to false to disable.maxSectionsPerPage report. During synchronization. Default is 300. and in reports generated by the Data Analyzer API. Set to false to display both the Summary and Grand Totals sections on the Analyze tab but hide these sections in reports emailed from the Find tab and in reports generated by the Data Analyzer API. Set to false only if you see problems with compressed content. Default is 65. If a report has more sections than the value set for this property. Possible values are view or analyze. If you set the time interval to 0. The Service Manager considers the value set for this property as the batch size to copy the users. Determines whether Data Analyzer synchronizes the user list at startup. Default is view. Properties in DataAnalyzer. Default is 15. Default is 100.maxSectionSelectorValues report.batchsize Description Number of users that the PowerCenter Service Manager processes in a batch. Maximum number of sectional tables to display per page on the Analyze tab. If true. Determines the default tab on which Data Analyzer opens a report when users double-click a report on the Find tab. the Service Manager copies the users from the domain configuration database to the Data Analyzer repository in batches. Maximum number of attribute values users can select for a sectional report table. Default is true. Maximum number of rows to display for each page or section for a report on the Analyze tab. report. Default is false. Default is 720 minutes (12 hours).showSummary report. Data Analyzer synchronizes the user list when it starts. If a report contains more sectional tables than this number. in reports emailed from the Find tab. Determines whether the servlet compresses files. or is set to false.properties Property ReportingService. Data Analyzer displays the sections on multiple pages. Data Analyzer displays all sections on the Analyze tab. You can add this property to DataAnalyzer. Set to true to display the Summary section and hide the Grand Totals section on the Analyze tab. Set to true to enable servlet compression.syncOnSystemStart servlet.Table B-1. including synchronization at startup.

Determines whether the server verifies that the browser contains an Accept-Encoding header and thus supports compression before sending a compressed response. Set to true to allow the server to send compressed files without checking for browser support. the data source is DB2. Set to true to display the header section.ConfigurationName. useDateConversionOnPrimaryDate uiconfig.ShowHeader uiconfig. and this property is set to the default value of false. including the logo. servlet. Set to true to enable servlet compression of JavaScript. For more information about enabling global caching.properties” on page 130. Data Analyzer uses the primary date in date comparisons without any date conversion.ConfigurationName. you define a Date Only time dimension. Default is false.xml 137 . if the datatype of the primary date column in the table is TIMESTAMP.properties Property servlet.useCompressionThroughProxies TimeDimension. For example. navigation bar. a date conversion is necessary to avoid SQL errors. Determines whether to display the header section for the Data Analyzer pages. In this case. Set to false to force the server to check if the browser can handle compression before sending compressed files. The date conversion ensures that Data Analyzer accurately compares dates.GlobalCaching property in DataAnalyzer.Date and time as separate attributes in same table Determines whether Data Analyzer converts a primary date column from date and time to date before using the primary date in SQL queries with date field comparisons. Determines whether to display the Data Analyzer navigation bar for the given configuration. However.compress. Properties in DataAnalyzer. Set to false to hide the header section. Set to false to disable. To ensure that Data Analyzer always converts the primary date column to DATE before using it in date comparisons. set this property to true.properties determines whether global caching is enabled for Data Analyzer. but can have impact on performance. and logout links. see “Properties in DataAnalyzer.ShowNav Properties in infa-cache-service. Set to false to hide the navigation bar. DB2 generates an error when Data Analyzer compares the primary date column with another column that has a DATE datatype. Default is true.Table B-1. Set to false only if you see problems with compressed JavaScript. Setting ShowHeader to false implicitly sets ShowNav to false.Date and time in separate tables . Properties in infa-cache-service.jscriptContentEncoding Description Determines whether the servlet compresses JavaScript loaded by <script> tags through content-encoding for browsers that support this compression. Default is false.Date only . help. for the given user interface configuration. The Cache. Set this property to false if the primary date is stored in a DATE column and date conversion is not necessary. Set to true to display the navigation bar. Applicable to the following types of time dimension: . Set to true only all browsers used by Data Analyzer users support compression.xml A cache is a memory area where frequently accessed data can be stored for rapid access.

<attribute name=”LockAcquisitionTimeout”>10000</attribute> 138 Appendix B: Configuration Files . Data Analyzer retrieves the object from the repository and then stores the object in memory. For more information about JBoss Cache. the LockAcquisitionTimeout attribute is set to 10. 3.xml to configure the following global cache features: ♦ ♦ Lock acquisition timeout Eviction policy If you disable global caching in the Cache. Use infa-cache-service.xml. locate infa-cache-service. the properties in infa-cache-service. Data Analyzer ignores the properties in infa-cache-service. Data Analyzer retrieves the object from the global cache instead of the repository. By default. Data Analyzer creates a global cache in memory for repository objects accessed by Data Analyzer users. see the JBoss Cache documentation library: http://labs.properties. Although infa-cacheservice. The next time a user accesses the updated object. you can increase the value of the LockAcquisitionTimeout attribute. Data Analyzer releases the lock on the object node. When a user first accesses an object.xml determine how the global cache is configured. In the directory where you extracted the Data Analyzer EAR file. If Data Analyzer cannot acquire a lock during this time period. it rolls back the transaction and displays an appropriate message to the user. Data Analyzer acquires a lock on the object node when it commits the update or delete transaction to the repository. The next time a user accesses the same object. When global caching is enabled. Data Analyzer retrieves the object from the repository.jboss. A node contains the data for a single cached object. for example. If Data Analyzer frequently rolls back transactions due to lock acquisition timeouts.xml in the following directory: <PowerCenter_Install folder>/server/tomcat/jboss/server/informatica/ias/<reporting service name>/properties 2.000 milliseconds.xml contains a number of properties to support the global cache. Locate the following text: name=”LockAcquisitionTimeout” 4. a report or dashboard.xml determines how long Data Analyzer attempts to acquire a lock on an object node. Data Analyzer removes the object from the cache and then saves the updated object to the repository. Data Analyzer may not be able to acquire a lock on an object node in the global cache under the following conditions: ♦ ♦ Another user or background process has locked the same object node. To configure the lock acquisition timeout: 1. The LockAcquisitionTimeout attribute in infa-cache-service.GlobalCaching property in DataAnalyzer. Data Analyzer has lost the connection to the repository. When the transaction completes.When global caching is enabled.xml file with a text editor. If a user updates an object that exists in the global cache. only the properties documented in this section are supported by Data Analyzer. Open the infa-cache-service. Data Analyzer stores data in the global cache in a hierarchical tree structure consisting of nodes.com/portal/jbosscache/docs Configuring the Lock Acquisition Timeout The global cache uses an optimistic node locking scheme to prevent Data Analyzer from encountering deadlocks. Changes to the default values of the unsupported properties may generate unexpected results. Data Analyzer uses JBoss Cache to maintain the global cache for Data Analyzer. Change the attribute value according to your requirements. When a user modifies an object that exists in the global cache.

hierarchical. User profiles. Maximum number of objects stored in the specified region of the global cache. you can increase the maximum number of dashboards and decrease the maximum number of reports that Data Analyzer stores in the global cache. /DataConnectors. Global variables used in reports. indicators. Infa-cache-service. maxNodes Properties in infa-cache-service. For example. /DataSources. color schemes. Dashboard definitions. Default varies for each region.xml includes several eviction policy attributes. The eviction policy works on regions of the global cache. Operational. /Reports. Data connector definitions. For example. /Metrics.5. User specific objects defined for reports. /System.xml. Current time values for calendar and time dimension definitions. Default is 60 seconds. if a large number of concurrent users frequently access dashboards but not reports. Add infa-cache-service. For example. /Schemas.xml defines the following global cache regions: ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ ♦ /Dashboards. You can configure a different eviction policy for each region so that Data Analyzer caches more or less objects of a particular type. Configuring the Eviction Policy To manage the size of the global cache. gauges. Data source definitions. Save and close infa-cache-service. Each global cache region defined in infa-cache-service. /_default_. the /Reports region contains all cached reports. Eviction Policy Attributes Attribute wakeUpIntervalSeconds Description Frequency in seconds that Data Analyzer checks for objects to remove from the global cache.xml back to the Data Analyzer EAR file. Each global cache region contains the cached data for a particular object type. /Reports/Variables. /Attributes. delivery settings. and analytic schemas. and highlighting rules added by each user. Report definitions. For example. You can decrease this value to have Data Analyzer run the eviction policy more frequently. Access permissions on an object and data restrictions defined for users or groups. and contact information. /Security. and role definitions. /Trees. /Reports/User. Data Analyzer writes informational messages to a global cache log file when a region approaches its maxNodes limit.xml 139 . Set the value to 0 to have Data Analyzer cache an infinite number of objects. /Users. You can modify these attributes to customize when Data Analyzer removes objects from the global cache. group definitions. Data Analyzer uses an eviction policy to remove the least frequently used objects from the cache when the cache approaches its memory limit. Content folder definitions in the Find tab. 6. Metric definitions. Calendar and time dimension definitions. Default region if an object does not belong to any of the other defined regions. /Time. Administrative system settings. Table B-2 lists the eviction policy attributes you can configure for the global cache: Table B-2. logs. Attribute definitions.

infa-cache-service. maxAgeSeconds Data Analyzer checks for objects to remove from the global cache at the following times: ♦ ♦ The wakeUpIntervalSeconds time period ends. By default. Save and close infa-cache-service. Set the value to 0 to define no time limit. Defined for each region of the global cache. For example. infa-cache-service. Data Analyzer removes cached user data if it has not been accessed for 30 minutes. Add the infa-cache-service. modify the following lines: <region name="/Dashboards"> <attribute name="maxNodes">200</attribute> <attribute name="timeToLiveSeconds">0</attribute> <attribute name="maxAgeSeconds">0</attribute> </region> 7. you can define maximum age limits for the other regions so that Data Analyzer removes objects from the cache before the maxNodes limit is reached.xml defines an idle time limit only for regions that contain user specific data.xml file back to the Data Analyzer EAR file. For example. In the directory where you extracted the Data Analyzer EAR file. Data Analyzer removes the least recently used object from the region. Defined for each region of the global cache. locate infa-cache-service. locate the following text: region name="/Dashboards" 6. Maximum number of seconds an object can remain in the global cache. you can define idle time limits for the other regions so that Data Analyzer removes objects from the cache before the maxNodes limit is reached. Locate the region whose eviction policy you want to modify. To configure the eviction policy: 1. Change the attribute values for the region according to your requirements. Eviction Policy Attributes Attribute timeToLiveSeconds Description Maximum number of seconds an object can remain idle in the global cache. For example. A global cache region reaches its maxNodes limit. If Data Analyzer runs on a machine with limited memory.xml defines a maximum age limit for only the /_default_ region. Data Analyzer removes objects that have reached the timeToLiveSeconds or maxAgeSeconds limits.xml. Change the value of the wakeUpIntervalSeconds attribute according to your requirements. Data Analyzer also removes objects from any region that have reached the timeToLiveSeconds or maxAgeSeconds limits. 8. Open the infa-cache-service. If Data Analyzer runs on a machine with limited memory. Default varies for each region.xml file with a text editor. 9. 140 Appendix B: Configuration Files . Repeat steps 5 to 6 for each of the global cache regions whose eviction policy you want to modify. the /Users region has a timeToLiveSeconds value of 1. By default. 3.800 seconds (30 minutes).Table B-2. Default varies for each region. Set the value to 0 to define no time limit.xml in the following directory: <PowerCenter_Install folder>/server/tomcat/jboss/server/informatica/ias/<reporting service name>/properties 2. <attribute name="wakeUpIntervalSeconds">60</attribute> 5. to change the attribute values for the /Dashboards region. Locate the following text: name=”wakeUpIntervalSeconds” 4. to locate the /Dashboards region.

Default is 5. Properties in web. The directory must be a shared file system that all servers in the cluster can access. Default is true. Data Analyzer deletes the users and groups in the repository that are not found in the LDAP directory service.xml 141 . If you specify a new directory. Data Analyzer synchronizes only user accounts.xml file contains configuration settings for Data Analyzer. By default.xml Property enableGroupSynchronization Description If you use LDAP authentication. for an inactive session on the Login page. If you want to keep user accounts in the LDAP directory service but keep the groups in the Data Analyzer repository. during synchronization. not groups. for an inactive session. use the forward slash (/) or two backslashes (\\) as the file separator. Default is 100. Maximum number of groups or users Data Analyzer displays in the search results before requiring you to refine your search criteria.Properties in web. Data Analyzer resets the session timeout to the value of the session-timeout property. Directory where Data Analyzer stores temporary files. If the user does not successfully log in and the session remains inactive for the specified time period. you typically modify only specific settings in the file. You can specify a full directory path such as D:/temp/DA. login-session-timeout searchLimit session-timeout showSearchThreshold TemporaryDir Properties in web. Default is tmp_ias_dir.xml that you can modify: Table B-3. Maximum number of groups or users Data Analyzer displays before displaying the Search box so you can find a group or user. Default is 1000. When this property is set to false. Default is 30. in minutes. Session timeout. After the user successfully logs in. set this property to false so that Data Analyzer does not delete or add groups to the repository during synchronization. Data Analyzer terminates sessions that are inactive for the specified time period. You can modify this file to customize the operation of an instance of Data Analyzer. the session expires.xml The web. in minutes. Session timeout. Data Analyzer does not support a single backslash as a file separator. Although the web. Data Analyzer creates the directory in the following default directory: <PCAEInstallationDirectory>/JBoss403/bin/ To specify a path.xml file contains a number of settings. this property determines whether Data Analyzer updates the groups in the repository when it synchronizes the list of users and groups in the repository with the LDAP directory service. Table B-3 describes the properties in web. You must maintain the group information within Data Analyzer.

142 Appendix B: Configuration Files .

13 using wildcards 14 write permission 13 activity log configuring maximum rows 80. 135 saving 79 viewing and clearing 79 administrative reports adding to schedules 96 Administrator’s Dashboard 93 description 93 list and description 97 public folder 94 setting up 94 Administrator’s Dashboard dashboard for administrative reports 93 AIX performance tuning 105 alert.GlobalCaching property configuring 131 Cache.Minfontsize property configuring 132 clearing activity log 79 event-based schedule histories 34 time-based schedule histories 24 user log 78 color schemes assigning 78 background image URL 75 creating 76 customizing 74.level property configuring 131 application server description 2 arguments Import Export utility 66 attaching imported reports to event-based schedule 37 reports to event-based schedule 32 B background image URL background image location 75 business days default 29 setting 29 C cache See global cache Cache.compatibility.Subscription.Fontsize property configuring 132 Chart.MaxDataPoints property configuring 132 Chart.Fontname property configuring 131 Chart.NoOfDaysToExpire property configuring 131 cached reports adding administrative reports to schedules 96 attaching to schedule after importing 26 importing 55 Calendar business days 29 daily view 28 holidays 29 leap years 28 monthly view 28 viewing 28 weekly view 28 change permission See access permissions Chart.fromaddress property configuring 131 alerts modifying From email address 131 analytic workflows See also Data Analyzer User Guide importing reports 54 AND operator multiple data restrictions 16 api.INDEX A access permissions change permission 14 creating 14 defined 13 Delete permission 14 exclusive 14 inclusive 14 read permission 13 schedules 24 setting 9.Report. 118 images directory 75 143 .

datalength property configuring 133 date/time formats in localization 8 DB2 database performance tuning 101 default color scheme using 74 delete permission See access permissions deleting data restrictions 19. 37 time-based schedule histories 24 time-based schedules 25 disabling event-based schedules 35 time-based schedules 25 E enableGroupSynchronization property configuring 141 error messages Import Export utility 69 event-based schedules access permissions 24 attaching imported reports 37 attaching reports 32 creating 32 defined 21 disabling 35 enabling 35 histories 34 managing reports 35 removing 35 schedule monitoring 29 starting immediately 34 stopping 35 stopping immediately 30 using PowerCenter Integration utility 33 exclusive permissions See access permissions exporting Data Analyzer objects dashboards 44 data restrictions 45 global variables 44 group security profile 45 metrics 40 overview 39 reports 42 security profile 45 time dimension tables 42 user security profile 45 using Import Export utility 65 external URL defined 83 registering 83 D daily view Calendar 28 dashboards exporting 44 importing 57 data access restricting 10.xml 137 web.compressThreshold property configuring 132 configuration files DataAnalyzer.OldBehavior property configuring 133 datatype. 20 exporting 45 importing 59 OR operator 16 data sources creating 94 creating for Metadata Reporter 94 description 3 data warehouses performance tuning 99 DataAnalyzer.properties 130 infa-cache-service.alwaysCompressMimeTypes property configuring 132 compressionFilter. 16 Data Analyzer performance tuning 111 data lineage using 5 data restrictions AND operator 16 by fact table 17 by user or group 19 deleting 19.MaximumNumberofColumns property configuring 132 DataRestriction.compressableMimeTypes property configuring 132 compressionFilter.list of color codes 121 login page image URL 75 logo image URL 75 primary 75 primary navigation 76 secondary 75 secondary navigation 76 selecting 77 using default 74 viewing 77 compression.transactionIsolationLevel property configuring 133 144 Index .properties configuring 130 datamart.defaultRowPrefetch property configuring 132 datamart.xml 141 contact information specifying for system administrator 84 creating event-based schedules 32 holidays 29 time-based schedules 22 CustomLayout.CLOB. 20 event-based schedule histories 34 event-based schedules 35 scheduled reports 27.

url property configuring 134 HP-UX performance tuning 102 L language settings backing up and restoring Data Analyzer repositories 7 Data Analyzer repository 7 data warehouse 7 import and export repository objects 8 importing table definitions 8 language support display 7 LDAP authentication server settings 81 synchronizing user list 136 leap years Calendar 28 Linux performance tuning 101 localization Data Analyzer display language 7 date and number formats 8 displaying reports in Chinese or Japanese when exporting to PDF 8 language settings 7 overview 7 setting metric or attribute default values 8 I images directory color scheme location 75 Import Export utility error messages 69 format 66 options and arguments 66 repository objects 68 running 66 using 65 import.xml file configuring 137 J Java environment viewing 84 JBoss Application Server description 2 JDBC log file 81. 11. 141 imported reports attaching to schedules 26 importing dashboards 57 data in multiple languages 8 data restrictions 59 global variables 56 group security profile 60 large XML files 62 overview 49 reports 54 schema objects 50 security profile 59 transaction timeout 62. 134 user security profile 59 using Import Export utility 65 inclusive permissions See access permissions Indicator.seconds property configuring 134 Index 145 .file property configuring 135 H header section UI configuration 118 headers configuring report headers 88 display options 88 heap size importing large XML files 63 help.log.pollingIntervalSeconds property configuring 134 infa-cache-service.files. 141 showSearchThreshold parameter 91.append property configuring 134 jdbc.F fact tables restricting data access 17 footers configuring report footers 88 display options 88 G global cache configuring 137 eviction policy 139 lock acquisition timeout 138 sizing 139 global variables exporting 44 importing 56 GroupBySuppression. 134 jdbc.GroupOnAttributePair property configuring 134 groups displaying 91 removing from the repository 10.timeout.log. 12 restricting data access 19 searchLimit parameter 91.url property configuring 134 histories clearing 34 clearing schedule 24 holidays creating 29 host.transaction.

135 login page image URL login page image location 75 login-session-timeout property configuring 141 logo image customizing 74 logo image location 75 P PDF.window property configuring 135 O operating system performance tuning 101 viewing 84 operational schemas setting data restrictions 17 operators AND 16 OR 16 options Import Export utility 66 OR operator multiple data restrictions 16 Oracle performance tuning 100 R read permissions See access permissions recurring schedules See time-based schedules 146 Index .ShrinkToWidth property configuring 135 using 89.maxRowsToDisplay property configuring 80.log files JDBC 81 managing 78 logging.Directory property configuring 135 metrics exporting 40 importing 50 Microsoft SQL Server 2000 performance tuning 101 monitoring schedules 29 monthly view Calendar 28 multiple instances of Data Analyzer configuration files 129 N navigation color schemes 76 navigation bar UI configuration 118 notifyias using in PowerCenter post-session command 33 Q queries setting rules 85 query governing query time limit 85 report processing time limit 85 row limit 85 setting rules 85 specifying for users 12 query time limit defined 85 queryengine.xml 141 providerContext.HeaderFooter.user.maxRowsToDisplay property configuring 79.abortThresHold property configuring 135 providerContext.xml 137 defining in web.properties 130 defining in infa-cache-service. 135 performance tuning AIX 105 Data Analyzer processes 111 database 99 DB2 database 101 HP-UX 102 Linux 101 Microsoft SQL Server 2000 101 operating system 101 Oracle database 100 Solaris 103 Windows 106 permissions See access permissions setting 9 post-session command using the PowerCenter Integration utility 33 PowerCenter Integration utility using in a post-session command 33 PowerCenter Workflow Manager using the PowerCenter Integration utility 33 predefined color scheme using 74 previewing report headers and footers 90 primary display item color scheme 75 properties defining in DataAnalyzer.maxInMemory property configuring 135 M mail servers configuring 83 Maps.estimation.activity. 135 logging.

compress.useCompressionThroughProxies property configuring 137 session-timeout property configuring 141 showSearchThreshold property configuring 141 single sign-on See also Data Analyzer SDK Guide with Data Analyzer API 118 single-event schedules See time-based schedules Solaris performance tuning 103 SQL queries row limit 85 setting rules 85 time limit 85 starting event-based schedules 34 time-based schedules 24 stopping event-based schedules 35 running schedules 30 time-based schedules 25 synchronization scheduler customizing 136 system administrator using Import Export utility 65 system information viewing 84 system log configuring 80 Index 147 .maxRowsPerTable property configuring 136 report.syncOnSystemStart property configuring 136 servlet.frequency property configuring 136 securityadapter. 36 schedules See also event-based schedules See also time-based schedules attaching imported reports to schedules 26 for cached administrative reports 96 stopping 30 scheduling business days 29 Calendar 28 holidays 29 schemas restricting data access 17 scroll bars report table option 88 searchLimit property configuring 141 secondary display item color schemes 75 security access permissions 13 security profiles exporting 45 exporting user 45 group 45 importing 59 importing group 60 importing user 59 securityadapter.batchsize configuring 136 reports See also Data Analyzer User Guide adding administrative reports to schedules 96 administrative reports overview 93 attached to time-based schedules 25 attaching imported reports to event-based schedule 37 attaching to event-based schedule 32 attaching to schedule after importing 26 deleting from time-based schedules 27 displaying scroll bars in tables 88 exporting Data Analyzer objects 42 header and footer display options 88 importing 54 in event-based schedules 35 list of administrative reports 97 previewing headers and footers 90 removing from event-based schedules 37 setting headers and footers 88 viewing in event-based schedule 36 viewing properties 27 repository database performance tuning 99 restore repository language settings 7 row limit query governing 85 row-level security restricting data access 16 running Import Export utility 66 S saving activity log 79 system log 80 user log 78 schedule monitoring defined 29 scheduled reports deleting 27 viewing 26.showSummary property configuring 136 report.userReportDisplayMode property configuring 136 ReportingService.compress property configuring 136 servlet.jscriptContentEncoding property configuring 137 servlet.removing See deleting report processing time limit defined 85 report.maxSectionSelectorValues property configuring 136 report.maxSectionsPerPage property configuring 136 report.

xml configuring 141 weekly view Calendar 28 wildcards searching user directory 14 Windows performance tuning 106 work days scheduling 29 write permissions See access permissions X XML files heap size for application 63 importing large files 62 temporary table space 63 U UI configuration default 118 properties 131 setting up 118. 141 UTF-8 character encoding Data Analyzer support 7 148 Index .useDateConversionOnPrimaryDate property configuring 137 timeout changing default for transactions 62 configuring for Data Analyzer session 4 transaction timeout changing the default 62 W web. 131 URL parameter 119 UICONFIG URL parameter 119 URL background image for color schemes 75 login page image for color schemes 75 logo image for color schemes 75 URL API See also Data Analyzer SDK Guide using 117 user log configuring maximum rows 79. 141 showSearchThreshold parameter 91.saving 80 viewing 80 V viewing activity log 79 histories for event-based schedules 34 reports attached to event-based schedules 36 reports attached to time-based schedules 26 system information 84 system log 80 time-based schedule histories 24 user log 78 T tasks properties 27 temporary table space importing large XML files 63 TemporaryDir property configuring 141 time dimension tables exporting Data Analyzer objects 42 time-based schedules access permissions 24 creating 22 defined 21 deleting 25 disabling and enabling 25 histories 24 managing reports 25 schedule monitoring 29 starting immediately 24 stopping immediately 25 viewing the Calendar 28 TimeDimension. 135 saving 78 viewing and clearing 78 users displaying 91 restricting data access 19 searchLimit parameter 91.

FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. INCLUDING BUT NOT LIMITED TO. INDIRECT. WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS. 2. INCLUDING. SPECIAL. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION. EITHER EXPRESSED OR IMPLIED. . IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT. NEGLIGENCE. BREACH OF CONTRACT. INCIDENTAL. an operating company of Progress Software Corporation (“DataDirect”) which are subject to the following terms and conditions: 1.NOTICES This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. STRICT LIABILITY. BREACH OF WARRANTY. WITHOUT LIMITATION. MISREPRESENTATION AND OTHER TORTS. THE IMPLIED WARRANTIES OF MERCHANTABILITY.

Sign up to vote on this title
UsefulNot useful