Data Analyzer Administrator Guide

Informatica® PowerCenter®
(Version 8.6.1)

Informatica PowerCenter Data Analyzer Administrator Guide Version 8.6.1 December 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 B2B Data Exchange and Informatica On Demand 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-86100-0001

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica How-To Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x 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
iii

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

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

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

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

. . . . . .xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Properties in DataAnalyzer. . . . . . . . . . . . . . . . . . . . . . . .xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Configuring the Eviction Policy . . . . . . . . . . . . . . . . . . . . . . . 137 Properties in web. . . . . .Modifying the Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .properties . . . . . . . . . . . . 128 Properties in infa-cache-service. . . . . . . . . . 141 viii Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Configuring the Lock Acquisition Timeout . . . . . .

including managing user access and report schedules and exporting and importing objects in a Data Analyzer repository. The How-To Library is a collection of resources to help you learn more about Informatica products and features. upcoming events. you can access the Informatica How-To Library at http://my. It also discusses performance tuning and server clusters. You will also find product and partner information. Informatica Resources Informatica Customer Portal As an Informatica customer.com. and web technology. The site contains information about Informatica.informatica. and sales offices. Informatica Web Site You can access the Informatica corporate web site at http://www. Informatica How-To Library As an Informatica customer. The services area of the site includes important information about technical support. access to the Informatica customer support case management system (ATLAS). the Informatica How-To Library.Preface The Data Analyzer Administrator Guide provides information on administering Data Analyzer. user group information. If you have questions. Let us know if we can contact you regarding your comments. comments. and access to the Informatica user community. compare features and behaviors. usable documentation. the Informatica Knowledge Base. We will use your feedback to improve our documentation. SQL.com. its background. It assumes that you have knowledge of relational databases. newsletters. and guide you through performing specific real-world tasks.informatica. Informatica Documentation The Informatica Documentation team takes every effort to create accurate. ix . contact the Informatica Documentation team through email at infa_documentation@informatica. training and education.com. and implementation services. you can access the Informatica Customer Portal site at http://my. or ideas about this documentation.com. Informatica Documentation Center. The site contains product information. It includes articles and interactive demonstrations that provide solutions to common problems. The Data Analyzer Administrator Guide is written for system administrators.informatica.

com for general customer service requests WebSupport requires a user name and password. technical white papers. Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Informatica Corporation Headquarters 100 Cardinal Way Redwood City. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. Berkshire SL6 3TN United Kingdom Asia / Australia Informatica Business Solutions Pvt. Use the following email addresses to contact Informatica Global Customer Support: support@informatica.informatica.Informatica Knowledge Base As an Informatica customer.informatica. You can also find answers to frequently asked questions.com for technical inquiries support_admin@informatica.com. Ltd.com. email. or the WebSupport Service. 6 Waltham Park Waltham Road. Diamond District Tower B. You can request a user name and password at http:// my. Informatica Global Customer Support There are many ways to access Informatica Global Customer Support. You can contact a Customer Support Center through telephone. you can access the Informatica Knowledge Base at http://my. 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 Spain and Portugal: +34 93 480 3760 United Kingdom: +44 1628 511 445 x Preface . California 94063 United States Europe / Middle East / Africa Informatica Software Ltd. White Waltham Maidenhead. and technical tips.

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

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

You can only modify the user settings such as the user name or the contact details in Data Analyzer. Note: You cannot create or delete users and groups. It connects to the database through JDBC drivers. see the PowerCenter Administrator Guide. When you use the Administration Console to create native users and groups. Data Analyzer reads data from an XML document. 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. or Metadata Manager. or it can be generated by a web service operation. PowerCenter Client tools. or by accessing the Data Analyzer URL from a browser. the Service Manager stores the users and groups in the domain configuration database and notifies the Reporting Service. You launch Data Analyzer from the Administration Console. or Metadata Manager Reports. reports and report delivery. Authentication Server You use PowerCenter authentication methods to authenticate users logging in to Data Analyzer. You log in to Data Analyzer to create and run reports on data in a relational database or to run PowerCenter Repository Reports. Data Analyzer Data Profiling Reports. you can extend the power of Data Analyzer when you set it up to work with these additional components. Forward reports through email. The XML document can reside on a web server. and other objects and processes. PowerCenter You create and enable a Reporting Service on the Domain page of the PowerCenter Administration Console. 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. Data Analyzer Framework 3 .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. Although you can use Data Analyzer without these components. personalization. Data Analyzer connects to the XML document or web service through an HTTP connection. the Administration Console starts Data Analyzer. user profiles. The Reporting Service copies the users and groups to the Data Analyzer repository. Data Analyzer reads data from a relational database. Data Analyzer connects to the repository with JDBC drivers. When you enable the Reporting Service. The metadata includes information on schemas. You can create reports based on the schemas without accessing the data warehouse directly. For more information about authentication methods. Data Source For analytic and operational schemas. or change user passwords in Data Analyzer. Supporting Components Data Analyzer has other components to support its processes. For hierarchical schemas.

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

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

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

To avoid data errors. Metadata Manager displays the data flow for that metric or attribute only. The data lineage also shows data structures for reports that use the metric or 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. Figure 1-2 show the data lineage for an attribute: Figure 1-2. Data Analyzer Display Language You can change the display language for the Data Analyzer client regardless of the locale of the Data Analyzer server. For a metric or attribute. see the Data Analyzer User Guide. Data structures for reports that use the attribute. The attribute name (Brand) appears within the data structure for the report. For more information about how to enable UTF-8 character encoding.Data Lineage for a Metric or Attribute The data lineage for a metric or attribute is similar to the data lineage for a report. For more information. Data Lineage for an Attribute The attribute name is the only field that appears in the data lineage. Language Settings When you store data in multiple languages in a database. You must change the display language for the Data Analyzer login page separately in the browser. UTF-8 character encoding is an ASCII-compatible multi-byte Unicode and Universal Character Set (UCS) encoding method. You change the display language for Data Analyzer in the Manage Accounts tab in Data Analyzer. A language setting is a superset of another language setting when it contains all characters encoded in the other language. 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 . 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. see the database documentation.

back up. For example, if the repository you back up contains Japanese data, the repository you restore to must also support Japanese. Import and export repository objects. When you import an exported repository object, the repositories must have the same language type and locale setting or the destination repository must be a superset of the source repository. Import table definitions from the data source. When you import data warehouse table definitions into the Data Analyzer repository, 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.

Setting the Default Expression for Metrics and Attributes
When you set the default expression for metrics and attributes, Data Analyzer uses the same expression regardless of the locale of the Data Analyzer server. If you want to use a different default expression for a different locale, you must change the default expression in the metric or attribute property. For more information, see the Data Analyzer Schema Designer Guide.

Date and Number Formats
The language setting for your Data Analyzer user account determines the numeric, date, and time formats Data Analyzer displays. When Data Analyzer performs date calculations in calculated or custom metrics, Data Analyzer uses the format for the repository database language setting. When you enter a date in an SQL expression or define a date value for a global variable, enter the date in the same format used in the data warehouse.

Exporting Reports with Japanese Fonts to PDF Files
If a report contains Japanese fonts and you export the report to a PDF file, you must download the Asian Font Package from the Adobe Acrobat web site to view the PDF file. Save the Asian Font Package on the machine where you want to view the PDF file. You can find the Asian Font Package from the following web site:
http://www.adobe.com/products/acrobat/acrrasianfontpack.html

8

Chapter 1: Data Analyzer Overview

CHAPTER 2

Managing Users and Groups
This chapter includes the following topics: Overview, 9 Managing Groups, 10 Managing Users, 11

Overview
You create users, groups, and roles in the PowerCenter domain configuration database. Use the Security page of the PowerCenter Administration Console to create users, groups, and roles for a Data Analyzer. For more information about creating users, groups, and roles, see the PowerCenter Administrator Guide. To secure information in the repository and data sources, Data Analyzer allows login access only to individuals with user accounts in Data Analyzer. A user must have an active account to perform tasks and access data in Data Analyzer. Users can perform different tasks based on their privileges. You can edit some user and group properties in Data Analyzer.

Restricting User Access
You can limit user access to Data Analyzer to secure information in the repository and data sources. Users in Data Analyzer need their own accounts to perform tasks and access data. Users can perform different tasks based on their privileges. You assign privileges to users, groups and roles in the Security page of the PowerCenter Administration Console.

Setting Permissions
You can set permissions to determine the tasks that users can perform on a repository object. You set access permissions in Data Analyzer.

Authentication Methods
The way you manage users and groups depends on the authentication method you are using: Native. You create and manage users, groups, and roles in the PowerCenter Administration Console. PowerCenter stores the users, groups, and roles in the domain configuration database.You can modify some user and group properties in Data Analyzer.

9

LDAP authentication. You manage the users and groups in the LDAP server but you create and manage the roles and privileges in the PowerCenter Administration Console. For more information about authentication methods, see the PowerCenter Administrator Guide.

User Synchronization
You manage users, groups, privileges, and roles on the Security page of the Administration Console. 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. The Service Manager periodically synchronizes the list of users and groups in the repository with the users and groups in the domain configuration database.
Note: If you edit any property of a user other than roles or privileges, the Service Manager does not synchronize the changes to the Data Analyzer repository. Similarly, if you edit any property of a user in Data Analyzer, the Service Manager does not synchronize the domain configuration database with the modification.

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, the Service Manager stores the privilege, role, and permission assignments with the list of users and groups in the Data Analyzer repository. The Service Manager periodically synchronizes users in the LDAP server with the users in the domain configuration database. In addition, the Service Manager synchronizes the users in the Data Analyzer repository with the updated LDAP users in the domain configuration database. For more information, see the PowerCenter Administrator Guide.

Managing Groups
Groups allow you to organize users according to their roles in the organization. For example, you might organize users into groups based on their departments or management level. You manage users and groups, their organization, and which privileges and roles are assigned to them in the PowerCenter Administration Console. You can restrict data access by group.

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. In Data Analyzer, you can edit some group properties such as department, color schemes, or query governing settings. You cannot add users or roles to the group, or assign a primary group to users in Data Analyzer.
To edit a group in Data Analyzer: 1. 2.

Connect to Data Analyzer from the PowerCenter Administration Console, PowerCenter Client tools, Metadata Manager, or by accessing the Data Analyzer URL from a browser. Click Administration > Access Management > Groups. The Groups page appears.

3.

Select the group you want to edit and click Edit. The properties of the group appear.

10

Chapter 2: Managing Users and Groups

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

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

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

Use the following methods to set access permissions: Inclusive. and default access permissions to create comprehensive access permissions for an object. a composite report might contain some subreports that do not display for all users. 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. By default. 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 .. Change permission. When you modify the access permissions on a folder. Setting access permissions for a composite report determines whether the composite report itself is visible but does not affect the existing security of subreports. you can grant the Analysts group inclusive access permissions to delete a report. Allows you to change the access permissions on a folder or object. Restrict access from the users and groups that you select.. For example. use exclusive access permissions. then set the access permissions for the user you select. To grant more extensive access to a user or group. You can completely restrict the selected users and groups or restrict them to fewer access permissions. Navigate to a repository object you want to modify. If you have reports and shared documents that you do not want to share. Therefore. For example. you can override existing access permissions on all objects in the folder. Users or groups must also have permissions to view individual subreports. To restrict the access of specific users or groups.Delete. Data Analyzer grants Read permission to every user in the repository. Allows you to delete a folder or an object from the repository. including subfolders. and use an exclusive Read permission to deny an individual in the Sales group access to the folder. For example.. You can use a combination of inclusive. You can also permit additional access permissions to selected users and groups. you can use exclusive access permissions to restrict the Vendors group from viewing sensitive reports. use inclusive access permissions. Permit access to the users and groups that you select. Exclusive. 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. To grant access permissions to users.. To set access permissions: 1. grant the Sales group inclusive write permission to edit objects in the folder. save them to your Personal Folder or your personal dashboard. search for the user name. exclusive. you can select Read as the default access permission for a folder.

you can select Replace Permissions on Subfolders to apply access permission changes to all subfolders. Select the access permissions you want to include or exclude. 5. -orClick Exclude to exclude the user or group from the access permissions you select. 3. Click the Permissions button ( ) for the repository object.To set access permissions on. Click Make a Selection to search for a group or user. The Query Results field displays groups or users that match the search criteria. 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. 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. 8. skip to step 4.. If you click Yes. If you are editing access permissions on an item. Setting Access Permissions 15 . set the default access permissions. Refine the selection by choosing the search criteria for the group or user. Note: Permissions set on composite reports do not affect permissions on the subreports. 9. click No to prevent all repository users from receiving default access permissions. Metric Attribute Template Dimension Click... If you are editing access permissions on a folder. Click Include to include the user or group in the access permissions you select. From the General Permissions area. 6. such as a report or shared document. You can select groups or users by criteria such as name or department. The object name appears in quotes. Click Yes to allow all users to receive the default access permissions you select. The Access Permissions page appears. Only those subreports where a user or group has access permissions display in a composite report. 7. Select the group or user in the Query Results field.

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

. 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. Understanding Data Restrictions for Multiple Groups A restricted user assigned to a restricted group is subject to both individual and group restrictions.. you cannot create data restrictions on fact tables or operational schemas using CLOB attributes. Data Analyzer handles data restrictions differently depending on the relationship between the two groups. Data Analyzer joins the restrictions with the AND operator.You can also use parentheses to create more complex groups of restrictions. Also. 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. you can group three data restrictions: Region NOT IN ‘North’ AND (Category IN ‘Footware’ OR Brand IN ‘BigShoes’) In the above example. if the user has the restriction Region IN ‘West’ and the user’s group has the restriction Region NOT IN ‘West’. 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. When you use a global variable in a data restriction. For example. Using Global Variables You can use global variables when you define data restrictions. For example. AND operator A user who belongs to. Restricting Data Access 17 . The following table describes how Data Analyzer handles multiple group situations: Data Analyzer joins data restrictions with.. Data Analyzer updates the data restriction when you update the global variable value.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

To start an event-based schedule immediately: 1.

Click Administration > Scheduling > Event-Based Schedules. The Event-Based Schedules page appears.

2.

For the event-based schedule you want to start, click Run Now. Data Analyzer starts the schedule and runs the attached reports.

Stopping an Event-Based Schedule Immediately
You can stop an event-based schedule immediately, which stops all attached reports. You can stop a schedule immediately when you need to restart the server. For more information, see “Stopping a Schedule” on page 30.

Disabling an Event-Based Schedule
You can disable an event-based schedule when you do not want it to run. You might disable a schedule when it has no attached reports or when the update of source data has been interrupted. When you want the schedule to resume, you can enable the schedule.
To disable an event-based schedule: 1.

Click Administration > Scheduling > Event-Based Schedules. The Event-Based Schedules page appears.

2.

Click the Enabled button for the schedule you want to disable. The Status of the schedule changes to Disabled. To enable the schedule again, click Disabled.

Removing an Event-Based Schedule
You can remove event-based schedules from the repository. You might want to remove an event-based schedule when the PowerCenter session is no longer valid. Before removing a schedule from the repository, reassign all attached reports to another schedule.
To remove an event-based schedule: 1. 2. 3.

Click Administration > Scheduling > Event-Based Schedules. Click the Remove button for the schedule you want to delete. Click OK.

Managing Reports in an Event-Based Schedule
After you create an event-based schedule, you can attach any cached reports to the schedule. When Data Analyzer runs an event-based schedule, it runs each attached report. You can perform the following tasks to manage reports in an event-based schedule: View a list of attached reports. View task properties. View or clear a report history. Remove a report from an event-based schedule. Attach imported cached reports to a schedule.

Managing Reports in an Event-Based Schedule

35

Viewing Attached Reports
You can view all reports attached to an event-based schedule.
To view tasks attached to an event-based schedule: 1.

Click Administration > Scheduling > Event-Based Schedules. The Event-Based Schedules page appears.

2.

Click the name of the schedule you want to edit. The schedule properties display.

3.

Click Tasks. Data Analyzer displays all attached reports.

Viewing Task Properties
You can view the properties of any report attached to an event-based schedule.
To view task properties: 1. 2. 3. 4.

Click Administration > Scheduling > Event-Based Schedules. Click the name of the schedule that runs the report. Click Tasks. Click the name of the report. The Task Properties page appears.

5.

Click OK.

Viewing or Clearing a Report History
You can view a report history for the reports attached to an event-based schedule. View report histories to determine how long a report takes to update, the number of successfully completed runs, or recurring errors when running the report. You might want to view a report history to compare the number of successful runs on different schedules. You can also clear report the history. You might clear history at the end of a quarter or to make space in the repository.
To view or clear a report history: 1. 2. 3. 4.

Click Administration > Scheduling > Event-Based Schedules. Click the name of the schedule that runs the report. Click Tasks. Click the name of the report. The Task Properties page appears.

5.

Click History. Data Analyzer displays the report history.

6. 7.

To clear the history, click Clear, and then click OK. To return to Task Properties, click OK.

36

Chapter 5: Managing Event-Based Schedules

Removing a Report from an Event-Based Schedule
You can remove a report from an event-based schedule. You might want to remove a report when you plan to disable the schedule or when the report requires a new update strategy. When you remove a cached report, attach it to another schedule to ensure it updates in a timely manner.
To remove a report from an event-based schedule: 1. 2. 3.

Click Administration > Scheduling > Event-Based Schedules. Click the name of the schedule you want to edit and then click Tasks. Select the check box for the report you want to remove. If you want to remove all attached reports, select the check box in the title bar next to Name.

4.

Click Remove, and then click OK.

Attaching Imported Cached Reports to an Event-Based Schedule
When you import cached reports to the repository, Data Analyzer displays the following message:
Some of the imported reports must be put on schedules. Please assign the reports to schedules immediately.

You must attach each imported cached report to a schedule. You can attach imported reports individually or attach multiple imported reports from a list to a single schedule. To attach multiple reports from the list, you must attach them during the same Data Analyzer session. If the session expires or you log out before attaching the reports from the import list, you cannot attach multiple reports. You must attach the imported reports individually. You can attach imported cached reports to time-based or event-based schedules.
To attach an imported cached report to an event-based schedule: 1. 2. 3.

Click Administration > Scheduling > Event-Based Schedules. Click the event-based schedule that you want to use. Click Tasks. The list of the tasks assigned to the schedule appears:

Appears when imported reports are not yet scheduled. Click to add the reports to existing schedules. 4.

Click Add. The Add button appears only when you have unscheduled imported reports in the repository. The Imported Scheduled Reports window appears.

5.

Select the reports that you want to add to the schedule. If you want to add all available imported reports to the schedule, click the All check box.

6.

Click Apply. The report appears as an item on the task list.
Managing Reports in an Event-Based Schedule 37

38 Chapter 5: Managing Event-Based Schedules .

40 Exporting a Time Dimension. 44 Exporting a Dashboard. 47 Overview You can export repository objects to XML files and import repository objects from XML files. You can view the XML files with any text editor. 42 Exporting a Global Variable. You can export the following repository objects: Schemas Time Dimensions Reports Global Variables Dashboards Security profiles Schedules When you export the repository objects. Data Analyzer creates an XML file that contains information about the exported objects. 44 Exporting a Security Profile. do not modify the XML file created when you export objects. Any 39 . Use this file to import the repository objects into a Data Analyzer repository.CHAPTER 6 Exporting Objects from the Repository This chapter includes the following topics: Overview. 45 Exporting a Schedule. You might also want to export and import objects to move Data Analyzer objects from development to production. 39 Exporting a Schema. 42 Exporting a Report. You might want to export objects to archive the repository. However. 46 Troubleshooting.

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

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

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

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

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

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

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

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

48 Chapter 6: Exporting Objects from the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Restart the application server. create a new system temporary table space with the page size of 32KB. enter the following: jdbc:datadirect:db2://<ServerName>:<PortNumber>. and then close the window. click Press Here to Continue. Click Connect. In the Database field. To resolve the error. To resolve the problem.bat UNIX: testforjdbc. log out of Data Analyzer and stop the application server. 10. Click Finish to complete the installation. enter the user name and password you use to connect to the repository database from Data Analyzer.4. Enter the following license key and click Add: eval 5. If you continue getting the same error message when you import large XML files. 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. 6. increase the value of the application heap size configuration parameter (APPLHEAPSZ) to 512. 11.sh 8. On the repository database. 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. run the Test for JDBC Tool: Windows: testforjdbc. ReplacePackage=TRUE. see the IBM DB2 documentation. Troubleshooting 63 .jar file. Restart the application server. Click Connection > Connect to DB. 9. see the IBM DB2 documentation. Click Next twice and then click Install. PortNumber is the port number of the database. you can run the Test for JDBC Tool again and increase the value of DynamicSections to 750 or 1000. For more information. In the testforjdbc folder. 12.CreateDefaultPackage=TRUE. DatabaseName is the name of the repository database. 7. The installation program for the DataDirect Connect for JDBC utility creates the testforjdbc folder in the directory where you extracted the connectjdbc. In the User Name and Password fields. On the Test for JDBC Tool window. 13. databaseName=<DatabaseName>. For more information.DynamicSections=500 ServerName is the name of the machine hosting the repository database.

64 Chapter 7: Importing Objects to the Repository .

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

Utility name. The default transaction time out for Data Analyzer is 3.transaction. To import or export users. open a command line window. For more information about repository object types. edit the value of the import. you must restart the application server. If you are importing large amounts of data from XML files and the transaction time is not enough.. the argument must follow the option letter. After you change this value. Use the -i or -e option. Go to the Data Analyzer utilities directory. Export a repository object type. Note: Back up the target repository before you import repository objects into it.seconds property in DataAnalyzer. see Table 8-2 on page 68. but not both. you must also have the Manage User Access privilege. Specify an option by entering a hyphen (-) followed by a letter.timeout. use the following rules: Specify the options in any order. run the utility as a shell command. 2. For more information about repository object types. you specify options and arguments to import or export different types of objects. To specify the options and arguments. On UNIX. You can back up a Data Analyzer repository with the Repository Backup utility. Table 8-1 lists the options and arguments you can specify: Table 8-1. Run the utility with the following format: Windows: ImportExport [-option_1] argument_1 [-option_2] argument_2 . UNIX: ImportExport. When you run the Import Export utility.Running the Import Export Utility Before you run the Import Export utility to import or export repository objects. you must have the System Administrator role or the Export/Import XML Files privilege.sh [-option_1] argument_1 [-option_2] argument_2 . To run the Import Export utility: 1. Data Analyzer must be running. The default directory is <PowerCenter_InstallationDirectory>/DataAnalyzer/import-exportutil/.. Use the -i or -e option. If any argument contains more than one word.600 seconds (1 hour). options. enclose the argument in double quotes. The first word after the option letter is the argument.. and argument names are case sensitive. To run the utility on Windows.. Options and Arguments for the Import Export Utility Option -i Argument repository object type Description Import a repository object type. but not both. If the option requires an argument. see Table 8-2 on page 68.0 or later. To change the default transaction time out for Data Analyzer. you must meet the following requirements: To run the utility. groups. You can use files exported from Data Analyzer 5. -e repository object type 66 Chapter 8: Using the Import Export Utility . you can change the default transaction time out value.properties. You can import Data Analyzer objects from XML files that were created when you exported repository objects from Data Analyzer. or roles.

com:16080/<ReportingServiceNa me> -u -p -l user name password url Data Analyzer user name. If you use this option when exporting repository objects. the utility saves the XML file in the path you specify. the utility exits without completing the operation. If you do not specify this option and if a repository object with the same name already exists. the utility displays an error message. If you do not use a hyphen when importing a security profile. when you enter the following command. see Table 8-2 on page 68. . The XML file must follow the naming conventions for the operating system where you run the utility.When you export an object type. For example.xml in the directory where you run the utility: ImportExport -e user -f Users. For example. Instructs the Import Export utility to overwrite existing repository objects of the same name. enter the following command: ImportExport -e user -f c:/PA/Users. Use to import or export the security profile of a user or group. and a list of valid repository objects. Running the Import Export Utility 67 . For example. Name of the XML file to import from or export to.xml -u admin -p admin -l http://my.com and has a Reporting Service named IASReports with port number 18080. the Import Export utility looks for the XML file in the directory where you run the utility.com:18080/IASReports -h -n No argument user name or group name Displays a list of all options and their descriptions.xml -u admin -p admin -l http://my.Table 8-1.When you import a repository object type. URL for accessing Data Analyzer. Options and Arguments for the Import Export Utility Option -w Argument No argument Description Import only. For more information. the utility places Users.server. to have the utility save the file in the c:/PA directory.ocean. 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. You can specify a path for the XML file. the Import Export utility looks for the XML file in the path you specify. . PowerCenter runs on a machine with hostname fish. the security profile being imported is appended to the existing security profile of the user or group.server. the utility saves the XML file in the directory where you run the utility.ocean.When you export an object type. Use the following URL for Data Analyzer: http://fish. Contact the system administrator for the URL.com:16080/<ReportingServiceNa me> -f XML file name If you do not specify a path for the XML file: . Password for the Data Analyzer user name.When you import a repository object type. If you specify a path for the XML file: .

Dashboards To export global variables to the GV. use the following command: ImportExport -e usersecurity -n jdoe -f JDsecurity. use the following command: ImportExport -e dashboard -f c:\Dash. You must specify the following security profile option: -n <group name> Schedules To export the security profile of user jdoe to the JDsecurity. You can import global variables that do not already exist in the repository. use the following command: ImportExport -i timedim -f TD. If the utility fails to complete the requested operation. use the following command: ImportExport -e groupsecurity -n Managers -f Profiles.xml file. use the following command: ImportExport -i report -f c:\Reports. 68 Chapter 8: Using the Import Export Utility . a message indicates that the process is successful.xml -u jdoe -p doe -l http://localhost:16080/<ReportingServiceName > timedim Time dimension tables To import time dimension tables from the TD. use the following command: ImportExport -e variable -f c:\xml\GV. Enter the repository object type as listed below: Table 8-2.xml file into the repository. Valid Repository Object Types Repository Object Type schema Description Schemas Example To import schemas from the PASchemas. use the following command: ImportExport -i schema -f c:\PASchemas.xml file. You must specify the following security profile option: -n <user name> Security profile of a group.xml -u admin -p admin -l http://localhost:16080/<ReportingServiceName > schedule To export all schedules to the Schedules.xml file. use the following command: ImportExport -e schedule -f c:\Schedules.xml file.xml file. an error message displays.xml -u jdoe -p doe -l http://localhost:16080/<ReportingServiceName > usersecurity <security profile option> Security profile of a user.xml -u jdoe -p doe -l http://server:16080/<ReportingServiceName> dashboard To export dashboards to the Dash.xml file into the repository. If the utility successfully completes the requested operation.xml -u jdoe -p doe -l http://localhost:16080/<ReportingServiceName > variable Global variables.xml -u jdoe -p doe -l http://localhost:16080/<ReportingServiceName > report Reports To import reports from the Reports.xml -u jdoe -p doe -l http://localhost:16080/<ReportingServiceName > The Import Export utility runs according to the specified options.xml file into the repository.xml -u admin -p admin -l http://localhost:16080/<ReportingServiceName > groupsecurity <security profile option> To export the security profile of group Managers to the Profiles.Table 8-2 lists the repository object types you can import or export using the Import Export utility and an example for each.

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

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

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

72 Chapter 8: Using the Import Export Utility .

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

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

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

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

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

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

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

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

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

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

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

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

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

Data Analyzer saves the user query governing settings. Click Administration > Access Management > Users. Data Analyzer uses the query governing settings for the group assigned to the user. Click the report whose properties you want to modify. 5. If a user belongs to multiple groups. user. see Table 9-3 on page 85. 86 Chapter 9: Managing System Settings .For more information about each setting. 4. To set up user query governing rules: 1. Query Governing Rules for Users in Multiple Groups If you specify query governing settings for a user. Data Analyzer saves the group query governing settings. 2. Query governing settings for the user override group and system query governing settings. see Table 9-3 on page 85. When you clear this option. In the Query Governing section. Click OK. For query time limit. 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. clear the Use Default Settings option. 2. For the row limit. Data Analyzer uses the setting for Group 3 since it is the least restrictive setting. Data Analyzer uses the query governing setting when it runs reports for the user. Setting Query Rules at the User Level You can specify query governing settings for all reports belonging to a specific user. Data Analyzer uses the query governing settings for the group that the user belongs to. you have not specifically configured query governing settings for a user. To set up report query governing rules: 1. 3. Click the user whose properties you want to modify. Click Edit. Data Analyzer assigns the user the least restrictive query governing settings available. If you do not specify query governing settings for a user. 5. Click the Find tab. 3. When this option is selected. Click OK. Enter the query governing settings you want to use. and system query governing settings. Setting Query Rules at the Report Level You can specify query governing settings for a specific report. Data Analyzer ignores groups with the system default query governing settings. Query governing settings for a specific report override group. For example. Data Analyzer uses the query governing settings entered on this page. Data Analyzer uses the setting for Group 1 since it is the least restrictive setting. For more information about each setting.

preview the report to verify that the headers and footers display properly with enough spaces between text or images. 7. 5. or Excel file. By default. Data Analyzer uses the query governing settings for the user. In the Query Governing section. Archive. Click Administration > System Management > Report Settings. When you enable the Show Scroll Bar on Report Table option. Display Options for Report Headers and Footers Header/Footer Left Header Center Header Display Options Text or image file. Data Analyzer uses the query governing settings entered on this page. Configuring Report Table Scroll Bars You can configure report tables to appear with a scroll bar. you can configure headers and footers for reports. When you select the headers and footers to display. Headers and footers display on the report when you complete the following report tasks: Print. Headers and footers display when you archive a report as an HTML. clear the Use Default Settings option. To change report table scroll bar display: 1. select Show Scroll Bar on Report Table. To disable scroll bars. You can display text or images in the header and footer of a report. or report information such as report name. On the Report Properties tab. When this option is selected. PDF. When you clear this option. or Excel file. Configuring Report Headers and Footers In the Header and Footer page. Click Save. Broadcast. Configuring Report Table Scroll Bars 87 .4. You can configure Data Analyzer to display text. PDF. you use the browser scroll bar to navigate large report tables. Email. Export. Data Analyzer displays a scroll bar when data in a report table extends beyond the size of the browser window. Click Publish. For more information about each setting. 6. Headers and footers display when you export to an HTML or PDF file. 8. Text. 2. To allow scroll bars. images. see Table 9-3 on page 85. Headers and footers display when you email a report as an HTML or PDF file. Headers and footers display when you broadcast a report as an HTML. Headers and footers display in the printed version of the report. clear the option. Enter the query governing settings you want to use. When the option is disabled. Data Analyzer displays scroll bars in report tables. Table 9-4 lists the options you can select to display in the report headers and footers: Table 9-4. Click Apply. The Report Settings page appears. click More Options. 3.

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

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

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

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 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 quickly see how well Data Analyzer is working and how often users log in. 92 Using the Data Analyzer Administrative Reports. Provides information on the number of users who logged in for the day. Administrator’s Dashboard The Administrator’s Dashboard displays the indicators associated with the administrative reports. They include details on Data Analyzer usage and report schedules and errors. They also require a data connector that includes the Data Analyzer administrative reports data source and operational schema. You can view the administrative reports in two areas: Administrator’s Dashboard. The Administrator’s Dashboard has the following containers: Today’s Usage. 91 . or change the format of any report. The reports provide a view into the information stored in the Data Analyzer repository. Data Analyzer Administrative Reports folder. You can access all administrative reports in the Data Analyzer Administrative Reports public folder under the Find tab. 95 Overview Data Analyzer provides a set of administrative reports that enable system administrators to track user activities and monitor processes. and any errors encountered when Data Analyzer runs cached reports. After you set up the Data Analyzer administrative reports. you can modify it to add metrics or attributes. They require a data source that points to the Data Analyzer repository. You can enhance the reports to suit your needs and help you manage the users and processes in Data Analyzer more efficiently. If you need additional information in a report. On the Administrator’s Dashboard. You can add charts or indicators. 91 Setting Up the Data Analyzer Administrative Reports.

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

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

2. To review the schedule for a report in the Data Analyzer Administrative Reports folder. 10. 3. Click Add. you need to create a data source for the repository. 6. In the Available Schemas section. click Public Folders. select Cached. 5. 7. verify that the cached reports are assigned to the appropriate schedules. and then select Hourly Refresh from the list of schedules. Click OK. Click Edit. Step 4. The Midnight Daily schedule is one of the schedules created when you install Data Analyzer. After you complete the steps to add the reports to the schedules. 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. 8. select the administrative reports data source you created earlier. Data Analyzer displays the additional schema mapping for the system data connector. In the Data Source list. On the Properties tab. select a report and look at the Report Properties section. Select a report to add to a schedule. 4. 94 Chapter 10: Working with Data Analyzer Administrative Reports . The public folder named Data Analyzer Administrative Reports contains the administrative reports. You can now run the administrative reports using the system data connector. 5. Save the report. The report appears in the Create Report wizard. Click Publish. 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. select PA_Reposit and click Add >>. After you import all the necessary objects for the administrative reports. 6. To add the administrative reports to schedules: 1. In the folders section of the Find tab. After you schedule the administrative reports. The PA_Reposit operational schema is one of the schemas installed by the PowerCenter Reports installer. Locate and click the folder named Data Analyzer Administrative Reports. 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. 9. Click the Find Tab.4. 7.

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

Use this report to determine how often users log in to Data Analyzer. Data Analyzer updates this cached report based on the Midnight Daily schedule. This report provides information about users who have never logged in to Data Analyzer. 96 Chapter 10: Working with Data Analyzer Administrative Reports . You can access this report from the Admin Reports container on the Administrator’s Dashboard and from the Find Tab. Data Analyzer updates this cached report based on the Hourly Refresh schedule. This report provides the number of errors Data Analyzer encountered when running cached reports. Use this on-demand report to view the user logs. This report displays the number of times each user logged in during the month. Use this report to make administrative decisions about disabling accounts. You can access this report from the Today’s Usage container on the Administrator’s Dashboard and from the Find Tab.can access this report from the Historical Usage container on the Administrator’s Dashboard and from the Find Tab. User Logins (Month To Date). You can access this report from the Find tab. Users Who Have Never Logged On. You can access this report from the Historical Usage container on the Administrator’s Dashboard and from the Find Tab. Total Schedule Errors for Today. Use this report to monitor cached reports and modify them if necessary. User Log Details.

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 97 .CHAPTER 11 Performance Tuning This chapter includes the following topics: Overview. 97 Database. Data Analyzer stores metadata in a repository database to keep track of the processes and objects it needs to handle web browser requests. Data Analyzer is built on JBoss Application Server and uses related technology and application programming interfaces (APIs) to accomplish its tasks. such as the enterprise data warehouse and authentication server. 97 Operating System. 109 Overview Data Analyzer requires the interaction of several components and services. 104 Data Analyzer Processes. 99 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. including those that may already exist in the enterprise infrastructure. JBoss Application Server is a Java 2 Enterprise Edition (J2EE)compliant application server.

periodically run the following command for the repository schema: EXEC DBMS_STATS. If the Data Analyzer instance has a high volume of usage.estimate_percent=>100). 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. you may need to use different values for the parameters than those recommended here. Raise the value of the pga_aggregate_target parameter from 32 MB to 64 MB (67108864). raise the maximum user process (maxuprc) limit from the default of 75 to at least 300. 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. Use the System Administration Manager tool (SAM) to raise the maxuprc limit. Shared Pool and Database Cache Size For optimal performance. The following repository database tuning recommendations are valid only for a repository that resides on a database server separate from the data warehouse. The data warehouse contains the data for the Data Analyzer reports. Updating the database parameters requires database administrator privileges. 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. see the Oracle documentation. To enable more connections to the Oracle repository. However. This section provides recommendations for tuning the Data Analyzer repository database for best performance. it has a very high volume of data. 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. cascade=>true.The repository database contains the metadata that Data Analyzer uses to construct reports. If you have the Data Analyzer repository database and the data warehouse in the same database server.GATHER_SCHEMA_STATS(ownname=><RepositorySchemaName>. 98 Chapter 11: Performance Tuning . The execution time of the reports depends on how well tuned the database and the report queries are. 2. Typically. since Data Analyzer executes many SQL transactions against the repository.ora file: Raise the value of the processes parameter from 150 to 300. The data warehouse is where the report SQL queries are executed. Statistics To ensure that the repository database tables have up-to-date statistics. the repository database must also be properly tuned to optimize the database performance. Oracle This section provides recommendations for tuning the Oracle database for best performance. raise the values for the following database parameters in the init. In Oracle. Raising the maxuprc limit requires root privileges. User Connection For an Oracle repository database running on HP-UX. You need to restart the machine hosting the Oracle repository for the changes to take effect. complete the following steps: 1. At the HP-UX operating system level. Note: Host the Data Analyzer repository and the data warehouse in separate database servers. You need to restart Oracle for the changes to take effect.

Operating System For all UNIX operating systems.boulder. Use the ulimit command to set the file descriptor limit. For optimal performance. make sure the file descriptor limit for the shell running the application server process is set to at least 2048.html?Open Microsoft SQL Server 2000 To ensure that repository database tables and indexes have up-to-date statistics. If you do not update table statistics periodically.IBM DB2 To ensure that the repository database tables have up-to-date statistics.local Operating System 99 . periodically run the sp_updatestats stored procedure on the repository schema.ibm. 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. Linux To optimize Data Analyzer on Linux. Enlarge the maximum open file descriptors. The following recommendations for tuning the operating system are based on information compiled from various application server vendor web sites. 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. To change these parameters. Enlarging Shared Memory and Shared Memory Segments By default. refer to the following IBM Redbook: http://publib-b. 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.com/Redbooks. you may encounter transaction deadlocks during times of high concurrency usage. you need to make several changes to your Linux environment. Enter the following commands to make them permanent: # echo '#Tuning kernel parameters' >> /etc/rc. Enlarge the maximum per-process open file descriptors.d/rc. 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. Linux limits the amount of memory and the number of memory segments that can be shared among applications to a reasonably small value. periodically run the following command for the repository schema: REORGCHK UPDATE STATISTICS on SCHEMA <DBSchemaName> Analysis of table statistics is important in DB2.nsf/RedbookAbstracts/sg246432.

d/rc.hp.conf 'session required /lib/security/pam_limits.d/rc.d/login Additional Recommended Settings Table 11-1 shows additional recommended settings for Linux operating system parameters: Table 11-1.00.www2.# echo 'echo "2147483648" > /proc/sys/kernel/shmmax' >> /etc/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. Enter the following commands to make them permanent: # echo 'echo "65536" > /proc/sys/fs/file-max' >> /etc/rc.local Enlarging the Maximum Per-Process Open File Descriptors Increase the maximum number of open files allowed for any given process. You can download the configuration utility from the following HP web site: http://h21007.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.d/rc. 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 100 Chapter 11: Performance Tuning . this is set to 4096 files.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.so' >> /etc/pam. Recommended Settings for Linux Parameters Linux Parameters /sbin/ifconfig lo mtu kernel.conf '* hard nofile 4096' >> /etc/security/limits.local # echo 'echo "250 32000 100 128" > /proc/sys/kernel/sem' >> /etc/rc.1701.ipv4.conf '* soft nofile 4096' >> /etc/security/limits.msgmni net. 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.1620. By default.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1.

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

When many clients connect for a short period of time. the tcp_time_wait_interval parameter was called tcp_close_ wait_interval. Change the default file descriptor limits.Table 11-3 lists the TCP-related parameters that you can tune and their recommended values: Table 11-3. Table 11-4 lists the /etc/system parameters that you can tune and the recommended values: Table 11-4. configure your operating system to have the appropriate number of file descriptors. and other tuning parameters in the /etc/system file. Setting this parameter to a value of 60000 (60 seconds) has shown a significant throughput enhancement when running benchmark JSP tests on Solaris. Setting Parameters in the /etc/system File Each socket connection to the server consumes a file descriptor. 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. Note: Restart the machine if you modify /etc/system parameters. 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 102 Chapter 11: Performance Tuning . the hash table size. holding these socket resources can have a significant negative impact on performance.7. You might want to decrease this setting if the server is backed up with a queue of half-opened connections. The default value of this parameter on Solaris is four minutes. This parameter determines the time interval that a TCP socket is kept alive after issuing a close call. To optimize socket performance.

Use the no and nfso commands to set the buffer sizes. 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.com/pseries/en_US/aixbman/prftungd/prftungd. AIX If an application on an AIX machine transfers large amounts of data.boulder. 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.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. you can increase the TCP/IP or UDP buffer sizes.net file. to set the tcp_sendspace parameter.htm Operating System 103 . add the commands to the /etc/rc. For more information about AIX tuning options. see the Solaris Tunable Parameters Reference Manual. see the Performance Management Guide on the IBM web site: http://publib16. 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. 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. 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. For example.Table 11-4.

If not specified. If not specified. minSpareThreads. However. then the following message may appear in the log files: ERROR [ThreadPool] All threads are busy. the parameter is set to 200. For additional information about configuring the Servlet/JSP container. which determines the maximum number of simultaneous requests that the Servlet/JSP container can handle. each of which has a different set of configuration files and parameters that can be tuned. modify the following configuration file: <PowerCenter_InstallationDirectory>/server/tomcat/jboss/server/informatica/deploy/jbossw eb-tomcat55. leading to faster response times. Maximum number of unused request processing threads that can exist before the pool begins stopping the unused threads. the parameter is set to 4.1 Connector on port 16080 --> <Connector port="16080" address="${jboss.sar/server. By default. leading to a general slow down of Data Analyzer. Decreasing the number of threads means that fewer users can use Data Analyzer concurrently.xml The following is a typical configuration: <!-.5 Servlet/JSP container. If not specified. more concurrent users may cause the application server to sustain a higher processing load. some users may need to wait for their HTTP request to be served.apache. Data Analyzer is configured to have a maximum of 250 request processing threads which is acceptable for most environments. Increasing the number of threads means that more users can use Data Analyzer concurrently.html 104 Chapter 11: Performance Tuning . Application Server JBoss Application Server consists of several components. 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. Data Analyzer may generate unexpected results if you modify properties that are not documented in this section.org/tomcat-5. However. Please increase maxThreads Although the Servlet/JSP container configuration file contains additional properties. 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. maxSpareThreads. waiting. Number of request processing threads initially created in the pool. the parameter is set to 50.bind. If the number of threads is too low.A HTTP/1. the Windows 2000 default settings for the TCP/IP parameters are adequate to ensure optimal network performance.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. Usually. Servlet/JSP Container JBoss Application Server uses the Apache Tomcat 5. see the Apache Tomcat Configuration Reference on the Apache Tomcat website: http://tomcat. Fewer concurrent users may alleviate the load on the application server.5-doc/config/index. Set the attribute to a value smaller than the value set for maxThreads. You can tune the Servlet/JSP container to make an optimal number of threads available to accept and process HTTP requests. Maximum number of request processing threads that can be created in the pool. To tune the Servlet/JSP container.

you can set the checkInterval parameter to specify when the JSPs are checked.jasper.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. When set to true.sar/conf/web. Checks for changes in the JSP files on an interval of n seconds. EJB Container Data Analyzer uses Enterprise Java Beans extensively. For more information about configuring thread management on JBoss Application Server. Stateless Session Beans For SLSBs. the JSP scripts must be compiled when they are executed for the first time. set it to 600 seconds. You can also define and configure thread handling in the JBoss Application Server configuration files. you can modify the following configuration file to optimize the JSP compilation: <PowerCenter_InstallationDirectory>/server/tomcat/jboss/server/informatica/deploy/jbossw eb-tomcat55. Typically.The Servlet/JSP container configuration file does not determine how JBoss Application Server handles threads. If you set the development parameter to true. In production environment.apache. The following is a typical configuration <container-configuration> <container-name> Standard Stateless SessionBean</container-name> <call-logging>false</call-logging> <invoker-proxy-binding-name> Application Server 105 . checks for modified JSPs at every access. checkInterval. the most important tuning parameter is the EJB pool. If you find that you need to compile the JSP files either because of customizations or while patching. Set the development parameter to false in a production installation. Informatica ships Data Analyzer with pre-compiled JSPs. JSP Optimization Data Analyzer uses JavaServer Pages (JSP) scripts to generate content for the web pages used in Data Analyzer. There are also six message-driven beans (MDBs) used for scheduling and real-time processes. This works only when the development parameter is set to true.xml. see the JBoss Application Server documentation. For example: <param-name>checkInterval</param-name> <param-value>99</param-value> Note: Make sure that the checkInterval is not too low.servlet. It has over 50 stateless session beans (SLSB) and over 60 entity beans (EB).xml The following is a typical configuration: <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org. You can tune the EJB pool parameters in the following file: <PowerCenter_InstallationDirectory>/server/tomcat/jboss/server/Informatica/conf/standard jboss. To avoid having the application server compile JSP scripts when they are executed for the first time.

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

resource. However.MetricsInterceptor</interceptor> <interceptor> org.<call-logging>false</call-logging> <invoker-proxy-binding-name>message-driven-bean </invoker-proxy-binding-name> <container-interceptors> <interceptor>org.plugins.jboss.jboss. Otherwise.jboss.TxInterceptorCMT</interceptor> <interceptor transaction="Container" metricsEnabled="true"> org.plugins.connectionmanager.ejb. If <strictMaximumSize> is set to true.jboss.xml.plugins.ejb.CachedConnectionInterceptor </interceptor> </container-interceptors> <instance-pool>org.jboss.ejb.ejb.LogInterceptor</interceptor> <interceptor>org.jboss. the number of active objects can exceed the <MaximumSize> if there are requests for more objects.ProxyFactoryFinderInterceptor </interceptor> <interceptor>org.plugins.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.plugins.MessageDrivenInstanceInterceptor </interceptor> <interceptor transaction="Bean"> org.ejb.plugins.plugins.plugins.plugins.ejb.ejb.MessageDrivenTxInterceptorBMT </interceptor> <interceptor transaction="Bean" metricsEnabled="true"> org. Represents the maximum number of objects in the pool. The EJB tuning parameters are in the following configuration file: <PowerCenter_InstallationDirectory>/server/tomcat/jboss/server/informatica/conf/standard jboss.ProxyFactoryFinderInterceptor </interceptor> <interceptor>org.BMT --> <interceptor transaction="Bean"> org. then <MaximumSize> is a strict upper limit for the number of objects that will be created.ejb. only the <MaximumSize> number of objects will be returned to the pool.plugins.jboss.LogInterceptor</interceptor> Application Server 107 . 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.plugins.ejb.ejb. if <strictMaximumSize> is set to false.MetricsInterceptor </interceptor> <interceptor transaction="Container"> org.jboss.MessageDrivenInstanceInterceptor </interceptor> <!-.jboss.jboss.CMT --> <interceptor transaction="Container"> org.jboss.plugins.RunAsSecurityInterceptor </interceptor> <!-.jboss. Enterprise Java Beans Data Analyzer EJBs use bean-managed persistence (BMP) as opposed to container-managed persistence (CMP).jboss.ejb.ejb.

jboss.EntitySynchronizationInterceptor </interceptor> </container-interceptors> <instance-pool>org.jboss. These parameters are not set by default in Data Analyzer. the <strictMaximumSize> parameter enforces a rule that only <MaximumSize> number of objects will be active.BMPPersistenceManager </persistence-manager> <locking-policy>org. Represents the maximum number of objects in the pool. When the value is set to true.ejb.plugins.QueuedPessimisticEJBLock </locking-policy> <container-cache-conf> <cache-policy>org. strictTimeout.jboss.jboss.MetricsInterceptor</interceptor> <interceptor>org.jboss.plugins.ejb.jboss.<interceptor>org.connectionmanager.ejb.ejb.plugins.plugins.TxInterceptorCMT </interceptor> <interceptor metricsEnabled="true"> org.plugins.ejb. then <strictTimeout> is the amount of time that requests will wait for an object to be made available in the pool. However.SecurityInterceptor </interceptor> <interceptor>org.EntityInstanceInterceptor </interceptor> <interceptor>org. the number of active objects can exceed the <MaximumSize> if there are requests for more objects.EntityCreationInterceptor </interceptor> <interceptor>org. if <strictMaximumSize> is set to false.jboss. Otherwise.EntityInstanceCache </instance-cache> <persistence-manager>org.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. If you set <strictMaximumSize> to true.ejb.ejb.ejb.jboss.plugins.jboss.plugins.lock. Any subsequent requests will wait for an object to be returned to the pool.plugins.plugins.jboss.ejb.CachedConnectionInterceptor </interceptor> <interceptor> org. You can set two other parameters to fine tune the EJB pool.jboss.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.ejb.EntityReentranceInterceptor </interceptor> <interceptor> org.EntityLockInterceptor </interceptor> <interceptor>org.jboss.EntityInstancePool </instance-pool> <instance-cache>org.resource. If <strictMaximumSize> is set to true. only the <MaximumSize> number of objects will be returned to the pool.ejb.jboss. then <MaximumSize> is a strict upper limit for the number of objects that will be created.ejb.jboss.plugins. 108 Chapter 11: Performance Tuning .ejb. They may be tuned after you have completed proper iterative testing in Data Analyzer to increase the throughput for high concurrency installations: strictMaximumSize.plugins.plugins.plugins.

If a high degree of precision is not required.Data Analyzer Processes To design schemas and reports and use Data Analyzer features more effectively. If the ranking is defined on a calculation that is performed in the middle tier. the report may take several minutes to display. A report with second level ranking. not including time. JDBC uses a different data structure when it returns data. Data Analyzer performs date manipulation on any column with a datatype of Date. Data Analyzer Processes 109 . JavaScript on the Analyze Tab The Analyze tab in Data Analyzer uses JavaScript for user interaction. 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. Data Analyzer includes conversion functions in the WHERE clause and SELECT clause to get the proper aggregation and filtering by date only. However. Data Analyzer runs another SQL query to get the aggregated values for the rows not shown in the report. then a BigDecimal format for columns in tables with a large volume of data adds unnecessary overhead. Datatype of Table Columns Data Analyzer uses JDBC drivers to connect to the data warehouse. If there are over 5. Data Analyzer may display messages warning that the JavaScripts on the page are running too slow. use the following guidelines. If a column contains date and time information. Data Analyzer has to pull all the data before it evaluates the calculation expression and ranks the data and filter. Also. If a column contains date information only. Use the Data Source is Timestamp property for an attribute to have Data Analyzer include conversion functions in the SQL query. consider making the report cached so that it can run in the background. On a slow workstation with a CPU speed less than 1 GHz. Set column datatypes to reflect the actual precision required. such as the top 10 products and the top five customers for each product. based on the column datatype defined in the database.000 cells in a report. Data Analyzer performance improves if the data warehouse contains good indexes and is properly tuned. Ranked Reports Data Analyzer supports two-level ranking. Date Columns By default. JDBC packages the returned data in a BigDecimal format. 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. 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. These types of reports consume resources and may slow down other Data Analyzer processes. If the report is defined to show Total Others at End of Table. If the report has one level of ranking. For optimal performance. 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. If you have a data warehouse with a large volume of data. If a report includes a column that contains date and time information but the report requires a daily granularity. If a column has a numeric datatype. conversion functions in a query prevent the use of database indexes and makes the SQL query inefficient. 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. avoid creating reports with ranking defined on custom attributes or custom metrics. create reports with two levels of ranking based on smaller schemas or on schemas that have good aggregate tables and indexes. which has a high degree of precision. Each cell in a report on the Analyze tab has embedded JavaScript objects to capture various user interactions.

you have five reports with user-based security and there are 500 security profiles for subscribers to the report. If you require reports to deliver real-time data. it may already have fetched hundreds of rows and stored them in the JVM heap. Data Analyzer cannot take advantage of parallel scheduler execution and sequentially generates the report for each security profile. Since a chart may use only a subset of the report columns and rows as a datapoint. performing time comparisons. Frequency of Schedule Runs Setting the report schedules to run very frequently. This means that each chart that Data Analyzer generates for a report has computing overhead associated with it. such as every five minutes. Data Analyzer runs only the tasks in an event in parallel mode.5 GHz. 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. To keep Data Analyzer from consuming more resources than necessary. Interactive Charts An interactive chart uses less application server resources than a regular chart. Data Analyzer generates a subset of the report dataset for each chart. However. You can control the number of rows displayed on a page in Layout and Setup. can create problems. Data Analyzer must pre-fetch all the rows so that the full dataset is available for operations such as ranking or ordering data. Although Data Analyzer displays only 20 rows in a page. On a typical workstation with a CPU speed greater than 2. Do not use the report schedules to frequently update reports to simulate real-time reports. an interactive chart can use up to 25% less CPU resources than a regular chart. Report designers who create a large number of charts to cover all possible user requirements can weaken the performance and scalability of Data Analyzer. If ReportA takes six minutes to run. To keep Data Analyzer scalable. On the machine hosting the application server. you add ReportA to a schedule that runs every five minutes. Data Analyzer must execute each of the five reports for each of the 500 security profiles. Number of Charts in a Report Data Analyzer generates the report charts after it generates the report table.Make sure that a report displayed in the Analyze tab has a restriction on the number of cells displayed on a page. For more information about editing your general preferences to enable interactive charts. see the Data Analyzer User Guide. For optimal performance. 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. For example. Use interactive charts whenever possible to improve performance. For example. use the real-time message stream features available in Data Analyzer. On the Formatting tab. 110 Chapter 11: Performance Tuning . Step 4 of the Create Report wizard. Within a task. Scheduler and User-Based Security Data Analyzer supports parallel execution of both time-based and event-based schedulers. set the number of rows to display per page for a report on the Analyze tab. or formatting reports into sections. This situation can drastically affect the performance of Data Analyzer. Data Analyzer starts running ReportA again before the previous run is completed. it is important to restrict the number of rows returned by the SQL query of a report. Since generating a report for each security profile is a subtask for each report. minimize the number of security profiles in Data Analyzer. consider the overhead cost associated with report charts and create the minimum set of charts required by the end user. Data Analyzer runs subtasks sequentially. interactive charts display at about the same speed as regular charts.

You can edit the providerContext. the memory requirements can be considerable. Data Analyzer runs the underlying report once. user level. limit the number of returned rows to a small value. the percentage of memory that is in use is 50%. You can edit the providerContext. you can set a threshold value between 50% and 99%. Data Analyzer keeps the datasets for all reports in a workflow in the user session.maxInMemory property in DataAnalyzer. Both for cached and ondemand reports. For example. These parallel threads are default threads spawned by the browser. When a user closes a browser window without logging out. Data Analyzer might run out of memory that results in the users getting a blank page. Typically. For more information about query governing. and the total memory configured for the JVM is 2. If there are a large number of concurrent users on Data Analyzer and each runs multiple reports. by default.abortThreshold property in the DataAnalyzer. is 30 minutes. Include only reports that have small datasets in a workflow. It uses a first in first out (FIFO) algorithm to overwrite reports in memory with more recent reports. Data Analyzer Processes 111 . If the percentage is above the threshold. Indicators in Dashboard Data Analyzer uses two parallel threads to load indicators in the dashboards. then Data Analyzer displays an error. The value must be greater than or equal to 2. at the server level. Data Analyzer loads all indicators based on cached reports before it loads indicators based on on-demand reports.000 KB. To calculate the percentage. Data Analyzer releases the memory after the expiration of session-timeout.abortThreshold When a user runs a report that involves calculation or building large result sets. If the amount of free memory does not meet a pre-defined percentage. You can increase the value for specific reports that require more data. Data Analyzer keeps two reports in the user session at a time. the default value of 2 is sufficient.000 KB. All indicators on a dashboard based on the same report use the same resultset. if the used memory is 1.properties to set the number of reports that Data Analyzer keeps in memory. which. Closing a browser window does not release the memory immediately. The default value is 95%. and report level. Data Analyzer saves the dataset returned by the report query in the user session until the user terminates the session. If the percentage is below the threshold.maxInMemory When a user runs a report.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. divide the used memory by the total memory configured for the JVM. Data Analyzer displays an error and stops processing the report request. You can set this parameter at the system level. Data Analyzer obtains the report model and the datapoint for the gauge at the same time and can immediately create the gauge. Set the value as low as possible to conserve memory. ProviderContext. Typically. To improve performance.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. Note: A user must log out of Data Analyzer to release the user session memory. it checks the amount of available memory. see “Setting Rules for Queries” on page 85. When there are multiple indicators based on a single report. Data Analyzer continues with the requested operation. By default. ProviderContext. 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 retains report results that are part of a workflow or drill path in memory irrespective of the value set in this property. such as 1000. 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. Before Data Analyzer starts calculating the report or building the tabular result set.

which results in very little overhead for rendering the table indicators on the browser. see “Managing System Settings” on page 73. use interactive charts on the dashboard. Chart Legends When Data Analyzer displays charts with legends.properties” on page 128. use indicators based on cached reports instead of on-demand reports. Depending on the number of legends in a chart. For on-demand reports. Position-based indicators can use indexes in the java collection for faster access of the database.maxCapacity=20 dynapool.000 rows. Data Analyzer records every user login in the user log.minCapacity=2 dynapool. consider displaying the chart without legends to improve Data Analyzer performance. To improve Data Analyzer performance. 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. Data Analyzer provides an estimate of the length of time a report takes to display. These logs can grow quickly.waitForConnectionSeconds=1 112 Chapter 11: Performance Tuning .The table indicators use plain HTML instead of DHTML. To optimize the database connection pool for a data source. Typically. whereas value-based indicators have to perform a linear scan of the rowset to match up the values. see “Properties in DataAnalyzer. dashboards provide summarized information. Data Analyzer uses the data in the activity log to calculate the Estimated Time to Run the Report for an on-demand report.properties. Use aggregate tables for indicators based on ondemand reports on the dashboards. Regular charts are rendered at server side and use the server CPU resources. modify the connection pool settings in DataAnalyzer. use the following recommendations: For dashboard indicators. In a high usage environment. Use position-based indicators instead of value-based indictors for reports with a volume of more than 2. Interactive charts are rendered on the browser and require much less server resources. Recommendations for Dashboard Design When you design a dashboard. you must clear these two logs frequently. Hence. For more information about managing the activity and user logs. the scan can get progressively slower for large datasets.evictionPeriodMins=5 dynapool. Connection Pool Size for the Data Source Data Analyzer internally maintains a pool of JDBC connections to the data warehouse. For most cases. You can specify the number of days that Data Analyzer uses for the estimate by editing the queryengine. it might take Data Analyzer from 10% to 50% longer to render a chart with legends. The following is a typical configuration: # Datasource definition # dynapool. the Data Analyzer charting engine must perform many complex calculations to fit the legends in the limited space available on the chart.estimation.window property in DataAnalyzer. For more information about the estimation window property. the default value of 30 days is fine. Purging of Activity Log Data Analyzer logs every activity or event that happens in Data Analyzer in the activity log. Similarly. If legends are not essential in a chart.properties. If the activity log contains a lot of data. This pool of JDBC connections is different from the pool of connections to the repository defined at the application server level.

network latency between the application server and the data warehouse must also be minimal. If the value is 0. There should also be minimal network latency between these servers. network latency between the application server and the repository database must be minimal. Data Analyzer runs only a few SQL queries against the data warehouse. Number of minutes that a connection may remain idle.evictionPeriodMins. Data Analyzer runs a large number of SQL queries against the repository to get the metadata before running any report. dynapool. Enter a positive value for this parameter. If you set a value less than the number of concurrent users. For optimal performance.connectionIdleTimeMins. Maximum number of connections that the data source pool can grow to. Default is 2. If you set the parameter to 0. It also becomes a single point of failure. Number of seconds Data Analyzer waits for a connection from the pool before it aborts the operation. since Data Analyzer runs a large number of them. This type of distributed architecture can be more economical because it can leverage existing infrastructure. have the repository database as close as possible to the application server Data Analyzer runs on. For optimal performance.defaultRowPrefetch=20 The following parameters may need tuning: dynapool. Although a single-machine architecture means that there is no network latency. However. Number of minutes between eviction runs or clean up operations during which Data Analyzer cleans up failed and idle connections from the connection pool.minCapacity. However. Set the value to the total number of concurrent users. Data Analyzer Processes 113 . Since the queries return many rows. Default is 1. frees the connections for report calculations.connectionIdleTimeMins so that Data Analyzer performs the eviction run. Minimum number of connections maintained in the data source pool.waitForConnectionSeconds. network latency is an issue in a distributed architecture. Data Analyzer creates a new connection to the data source to calculate a report. Note: Data Analyzer connects to only one repository database. The SQL queries that Data Analyzer runs against the data warehouse return many rows and are CPU and IO intensive. An alternative to the single-machine architecture is a distributed system where the servers are located on different machines across a network. You can set the value to half of the value set for the parameter dynapool.evictionPeriodMins is not set.dynapool. Typically. dynapool. dynapool. and does not allow a connection to remain idle for too long. it can connect to more than one data warehouse. Default is 10. Server Location and Network Latency There are two database components in Data Analyzer: the repository and data warehouse. these servers must have enough CPU power and RAM. The SQL queries that Data Analyzer runs against the repository are not CPU or IO intensive. Server Location Data Analyzer runs on an application server and reads data from a database server.maxCapacity. Default is 5 minutes.connectionIdleTimeMins=10 datamart. Data Analyzer does not wait and aborts the operation. However. If you set the parameter to 0 or a negative value. the data warehouse requires more CPU power than the repository database. Server Location and CPU Power and RAM If you locate the application server and database server in a single machine. dynapool. Data Analyzer returns an error message to some users. the machine must have enough CPU power and RAM to handle the demands of each of the server processes. Data Analyzer sets the parameter to the default value. Set to 0 to ensure that no connections are maintained in the data source pool. Data Analyzer ignores this property if the parameter dynapool. the requirements for a very powerful machine makes it an expensive solution.

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. As with any major software implementation project, carefully perform capacity planning and testing before a Data Analyzer deployment. The choice of architecture depends on the requirements of the organization. Make sure that all processes have enough resources to function optimally.

114

Chapter 11: Performance Tuning

CHAPTER 12

Customizing the Data Analyzer Interface
This chapter includes the following topics: Overview, 115 Using the Data Analyzer URL API, 115 Using the Data Analyzer API Single Sign-On, 116 Setting Up Color Schemes and Logos, 116 Setting the UI Configuration Properties, 116

Overview
You can customize the Data Analyzer user interface so that it meets the requirements for web applications in your organization. Data Analyzer provides several ways to allow you to modify the look and feel of Data Analyzer. You can use the following techniques to customize Data Analyzer: Use the URL API to display Data Analyzer web pages on a portal. Use the Data Analyzer API single sign on (SSO) scheme to access Data Analyzer web pages without a user login. Set up custom color schemes and logos on the Data Analyzer Administration tab. Set the user interface (UI) configuration properties in the DataAnalyzer.properties file to display or hide the Data Analyzer header or navigation bar.

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, such as dashboard, report, or tab pages. The URL consists of the Data Analyzer location and parameters that determine the content and interface for the Data Analyzer page. For more information about the Data Analyzer URL API, see the Data Analyzer SDK Guide.

115

Using the Data Analyzer API Single Sign-On
When you access Data Analyzer, the login page appears. You must enter a user name and password. Ordinarily, if you display Data Analyzer web pages in another web application or portal, the Data Analyzer login appears even if you have already logged in to the portal where the Data Analyzer pages are displayed. To avoid multiple logins, 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. The Data Analyzer API provides an SSO mechanism that you can use when you display Data Analyzer pages in another web application or portal. You can configure Data Analyzer to accept the portal authentication and bypass the Data Analyzer login page. For more information about the Data Analyzer API SSO, see the Data Analyzer SDK Guide.

Setting Up Color Schemes and Logos
Data Analyzer provides two color schemes for the Data Analyzer interface. 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. You can also create color schemes and use custom graphics, buttons, and logos to match the standard color scheme for the web applications in your organization. For more information, see “Managing Color Schemes and Logos” on page 74.

Setting the UI Configuration Properties
In DataAnalyzer.properties, you can define a user interface configuration that determines how Data Analyzer handles specific sections of the user interface. The UI configuration include the following properties:
uiconfig.<ConfigurationName>.ShowHeader=true uiconfig.<ConfigurationName>.ShowNav=true

The properties determine what displays in the header section of the Data Analyzer user interface which includes the logo, the logout and help links, and the navigation bar:

Navigation Bar

Header Section

Default UI Configuration
By default, when a user logs in to Data Analyzer through the Login page, the logo, logout and help links, and navigation bar display on all the Data Analyzer pages. To hide the navigation bar or the header section on the Data Analyzer pages, you can add a UI configuration named default to DataAnalyzer.properties and set the properties to false. To hide the whole header section, add the following property:
uiconfig.default.ShowHeader=false

To hide only the navigation bar, add the following property:
uiconfig.default.ShowNav=false 116 Chapter 12: Customizing the Data Analyzer Interface

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

118 Chapter 12: Customizing the Data Analyzer Interface .properties in the Data Analyzer EAR file.ShowHeader=true and ShowNav=false ShowHeader=false and ShowNav=false Note: Data Analyzer stores DataAnalyzer.

119 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. 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 119 . you can alter the colors in Data Analyzer to match your corporate color scheme.APPENDIX A Hexadecimal Color Codes This appendix includes the following topic: HTML Hexadecimal Color Codes. For more information about creating a color scheme. see “Managing Color Schemes and Logos” on page 74. Table A-1 lists the colors and hexadecimal color codes you can use when creating color schemes for Data Analyzer: Table A-1. For example.

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 120 Appendix A: Hexadecimal Color Codes .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 121 .Table A-1.

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

Table A-1. 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 124 Appendix A: Hexadecimal Color Codes .

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

Table A-1. 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 126 Appendix A: Hexadecimal Color Codes .

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

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

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

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

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

Properties in DataAnalyzer. URL for the location of Data Analyzer online help files. the installation process installs online help files on the same machine as Data Analyzer and sets the value of this property. 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.url import. Determines whether Data Analyzer waits for a database connection if none are available in the connection pool.seconds Indicator. the number of connections in the pool reverts to the value of its initialCapacity parameter if the allowShrinking parameter is true. By default. Default is true.shrinkPeriodMins dynapool. Set to true to append new messages. Default is true. Default is 5.files. dynapool. Number of minutes Data Analyzer allows an idle connection to be in the pool.properties Property dynapool. Default is true. URL for the Data Analyzer instance. 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. If the data source stores a dataset in a single row in a table. Maximum number of seconds a client waits to grab a connection from the pool if none is readily available before giving a timeout error. By default. Default is 300 seconds (5 minutes). For more information.transaction.Table B-1.waitForConnection dynapool.timeout.log. see the Data Analyzer User Guide.GroupOnAttributePair help. Default is 3600 seconds (1 hour). Set to true to group values by the row attributes. Determines whether to append or overwrite new log information to the JDBC log file.url host. 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. To import a large XML file. Default is 60. After this period. Set to false to overwrite existing information. you might need to increase this value.append 132 Appendix B: Configuration Files .pollingIntervalSeconds jdbc. Set to false if you do not want the Data Analyzer report to group the data based on the row attributes.waitSec GroupBySuppression.refreshTestMinutes Description Frequency in minutes at which Data Analyzer performs a health check on the idle connections in the pool. Frequency in seconds that Data Analyzer refreshes indicators with animation. the value of this property does not affect how the report displays. Default is 1.

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

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

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

xml determines how long Data Analyzer attempts to acquire a lock on an object node.properties.xml to configure the following global cache features: Lock acquisition timeout Eviction policy If you disable global caching in the Cache. The next time a user accesses the same object. Appendix B: Configuration Files . a report or dashboard. Data Analyzer has lost the connection to the repository. 3. 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 updated object. When global caching is enabled. <attribute name=”LockAcquisitionTimeout”>10000</attribute> 5. 136 Save and close infa-cache-service. Data Analyzer ignores the properties in infa-cache-service. Data Analyzer uses JBoss Cache to maintain the global cache for Data Analyzer. When the transaction completes. Data Analyzer retrieves the object from the global cache instead of the repository.xml. For more information about JBoss Cache. the LockAcquisitionTimeout attribute is set to 10. Data Analyzer retrieves the object from the repository and then stores the object in memory. If Data Analyzer cannot acquire a lock during this time period. Use infa-cache-service.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. Data Analyzer retrieves the object from the repository.jboss. The LockAcquisitionTimeout attribute in infa-cache-service.xml contains a number of properties to support the global cache. Data Analyzer stores data in the global cache in a hierarchical tree structure consisting of nodes. Locate infa-cache-service. When a user first accesses an object. you can increase the value of the LockAcquisitionTimeout attribute. Data Analyzer releases the lock on the object node. for example.xml. only the properties documented in this section are supported by Data Analyzer.xml determine how the global cache is configured. Data Analyzer creates a global cache in memory for repository objects accessed by Data Analyzer users.GlobalCaching property in DataAnalyzer. Locate the following text: name=”LockAcquisitionTimeout” 4. Open the infa-cache-service. A node contains the data for a single cached object. Although infa-cacheservice. see the JBoss Cache documentation library: http://labs. To configure the lock acquisition timeout: 1. Change the attribute value according to your requirements. the properties in infa-cache-service. If a user updates an object that exists in the global cache.000 milliseconds.xml in the following directory: <PowerCenter_InstallationDirectory>/server/tomcat/jboss/server/informatica/ias/<reportin g service name>/properties 2. If Data Analyzer frequently rolls back transactions due to lock acquisition timeouts. When a user modifies an object that exists in the global cache.When global caching is enabled. Changes to the default values of the unsupported properties may generate unexpected results. Data Analyzer removes the object from the cache and then saves the updated object to the repository.xml file with a text editor. By default. 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. it rolls back the transaction and displays an appropriate message to the user.

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

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

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

140

Appendix B: Configuration Files

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, 13 using wildcards 14 write permission 13 activity log configuring maximum rows 80, 133 saving 79 viewing and clearing 79 administrative reports adding to schedules 94 Administrator’s Dashboard 91 description 91 list and description 95 public folder 92 setting up 92 Administrator’s Dashboard dashboard for administrative reports 91 AIX performance tuning 103 alert.fromaddress property configuring 129 alerts modifying From email address 129 analytic workflows See also Data Analyzer User Guide importing reports 54 AND operator multiple data restrictions 16 api.compatibility.level property configuring 129 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.GlobalCaching property configuring 129 Cache.Report.Subscription.NoOfDaysToExpire property configuring 129 cached reports adding administrative reports to schedules 94 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.Fontname property configuring 129 Chart.Fontsize property configuring 130 Chart.MaxDataPoints property configuring 130 Chart.Minfontsize property configuring 130 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, 116 images directory 75

141

list of color codes 119 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.alwaysCompressMimeTypes property configuring 130 compressionFilter.compressableMimeTypes property configuring 130 compressionFilter.compressThreshold property configuring 130 configuration files DataAnalyzer.properties 128 infa-cache-service.xml 135 web.xml 139 contact information specifying for system administrator 84 creating event-based schedules 32 holidays 29 time-based schedules 22 CustomLayout.MaximumNumberofColumns property configuring 130

DataRestriction.OldBehavior property configuring 131 datatype.CLOB.datalength property configuring 131 date/time formats in localization 8 DB2 database performance tuning 99 default color scheme using 74 delete permission See access permissions deleting data restrictions 19, 20 event-based schedule histories 34 event-based schedules 35 scheduled reports 27, 37 time-based schedule histories 24 time-based schedules 25 disabling event-based schedules 35 time-based schedules 25

E
enableGroupSynchronization property configuring 139 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, 16 Data Analyzer performance tuning 109 data lineage using 5 data restrictions AND operator 16 by fact table 17 by user or group 19 deleting 19, 20 exporting 45 importing 59 OR operator 16 data sources creating 92 creating for Metadata Reporter 92 description 3 data warehouses performance tuning 97 DataAnalyzer.properties configuring 128 datamart.defaultRowPrefetch property configuring 130 datamart.transactionIsolationLevel property configuring 131

142

Index

url property configuring 132 HP-UX performance tuning 100 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 134 leap years Calendar 28 Linux performance tuning 99 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.files. 139 showSearchThreshold parameter 90. 132 user security profile 59 using Import Export utility 65 inclusive permissions See access permissions Indicator.timeout.xml file configuring 135 J Java environment viewing 84 JBoss Application Server description 2 JDBC log file 81.seconds property configuring 132 Index 143 .file property configuring 133 H header section UI configuration 116 headers configuring report headers 87 display options 87 heap size importing large XML files 63 help.log. 132 jdbc. 11.pollingIntervalSeconds property configuring 132 infa-cache-service.transaction.F fact tables restricting data access 17 footers configuring report footers 87 display options 87 G global cache configuring 135 eviction policy 137 lock acquisition timeout 136 sizing 137 global variables exporting 44 importing 56 GroupBySuppression.append property configuring 132 jdbc. 139 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.url property configuring 132 histories clearing 34 clearing schedule 24 holidays creating 29 host.GroupOnAttributePair property configuring 132 groups displaying 90 removing from the repository 10. 12 restricting data access 19 searchLimit parameter 90.log.

maxRowsToDisplay property configuring 79.HeaderFooter.user.Directory property configuring 133 metrics exporting 40 importing 50 Microsoft SQL Server 2000 performance tuning 99 monitoring schedules 29 monthly view Calendar 28 multiple instances of Data Analyzer configuration files 127 N navigation color schemes 76 navigation bar UI configuration 116 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. 133 logging.xml 135 defining in web. 133 login page image URL login page image location 75 login-session-timeout property configuring 139 logo image customizing 74 logo image location 75 P PDF.abortThresHold property configuring 133 providerContext.window property configuring 133 O operating system performance tuning 99 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 98 R read permissions See access permissions recurring schedules See time-based schedules 144 Index .ShrinkToWidth property configuring 133 using 88.xml 139 providerContext.activity.properties 128 defining in infa-cache-service.estimation. 133 performance tuning AIX 103 Data Analyzer processes 109 database 97 DB2 database 99 HP-UX 100 Linux 99 Microsoft SQL Server 2000 99 operating system 99 Oracle database 98 Solaris 101 Windows 104 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 89 primary display item color scheme 75 properties defining in DataAnalyzer.maxInMemory property configuring 133 M mail servers configuring 83 Maps.maxRowsToDisplay property configuring 80.log files JDBC 81 managing 78 logging.

frequency property configuring 134 securityadapter.removing See deleting report processing time limit defined 85 report.maxSectionSelectorValues property configuring 134 report.compress property configuring 134 servlet.showSummary property configuring 134 report.userReportDisplayMode property configuring 134 ReportingService.jscriptContentEncoding property configuring 135 servlet.maxRowsPerTable property configuring 134 report.compress.syncOnSystemStart property configuring 134 servlet. 36 schedules See also event-based schedules See also time-based schedules attaching imported reports to schedules 26 for cached administrative reports 94 stopping 30 scheduling business days 29 Calendar 28 holidays 29 schemas restricting data access 17 scroll bars report table option 87 searchLimit property configuring 139 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.maxSectionsPerPage property configuring 134 report.useCompressionThroughProxies property configuring 135 session-timeout property configuring 139 showSearchThreshold property configuring 139 single sign-on See also Data Analyzer SDK Guide with Data Analyzer API 116 single-event schedules See time-based schedules Solaris performance tuning 101 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 134 system administrator using Import Export utility 65 system information viewing 84 system log configuring 80 Index 145 .batchsize configuring 134 reports See also Data Analyzer User Guide adding administrative reports to schedules 94 administrative reports overview 91 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 87 exporting Data Analyzer objects 42 header and footer display options 87 importing 54 in event-based schedules 35 list of administrative reports 95 previewing headers and footers 89 removing from event-based schedules 37 setting headers and footers 87 viewing in event-based schedule 36 viewing properties 27 repository database performance tuning 97 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.

xml configuring 139 weekly view Calendar 28 wildcards searching user directory 14 Windows performance tuning 104 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 116 properties 129 setting up 116. 139 showSearchThreshold parameter 90. 129 URL parameter 117 UICONFIG URL parameter 117 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 115 user log configuring maximum rows 79. 133 saving 78 viewing and clearing 78 users displaying 90 restricting data access 19 searchLimit parameter 90.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 139 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.useDateConversionOnPrimaryDate property configuring 135 timeout changing default for transactions 62 configuring for Data Analyzer session 4 transaction timeout changing the default 62 W web. 139 UTF-8 character encoding Data Analyzer support 7 146 Index .

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

Sign up to vote on this title
UsefulNot useful