DA_861_AdministratorGuide | Application Server | Metadata

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

if the user has the restriction Region IN ‘West’ and the user’s group has the restriction Region NOT IN ‘West’. Restricting Data Access 17 .. you cannot create data restrictions on fact tables or operational schemas using CLOB attributes. 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 restrictions with the AND operator. AND operator A user who belongs to. Data Analyzer handles data restrictions differently depending on the relationship between the two groups. Also.. For example. For example. When you use a global variable in a data restriction..You can also use parentheses to create more complex groups of restrictions. The following table describes how Data Analyzer handles multiple group situations: Data Analyzer joins data restrictions with.. you can group three data restrictions: Region NOT IN ‘North’ AND (Category IN ‘Footware’ OR Brand IN ‘BigShoes’) In the above example. 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. Data Analyzer updates the data restriction when you update the global variable value. Both a group and its subgroup Example If Group A has the following restriction: Region IN ‘East’ And Subgroup B has the following restriction: Category IN ‘Women’ Data Analyzer joins the restrictions with AND: Region IN ‘East’ AND Category IN ‘Women’ Two groups that belong to the same parent group OR operator If Group A has the following restriction: Region IN ‘East’ And Group B has the following restriction: Category IN ‘Women’ Data Analyzer joins the restrictions with OR: Region IN ‘East’ OR Category IN ‘Women’ Restricting Data Access by Object Create data restrictions by object when you want to apply the restriction to more than one user or group or to create more than one data restriction for the object. Data Analyzer 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. Using Global Variables You can use global variables when you define data restrictions.

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

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

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

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

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

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

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

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

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

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

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

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

2. Data Analyzer displays schedules that are currently running. 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. Click Remove to stop a running schedule. 30 Chapter 4: Managing Time-Based Schedules . The Schedule Monitor lists all currently running schedules. Click OK. Click Administration > Scheduling > Schedule Monitoring. Stopping a Schedule You can stop a running schedule and all attached reports through the Schedule Monitor. To stop a running schedule: 1. 3.To monitor a schedule.

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

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

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

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

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 .

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

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

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

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

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

Therefore. Data Analyzer creates one XML file for the global variables and their default values. You can export any of the public dashboards defined in the repository. To export a dashboard: 1. Select the global variables that you want to export. Click Export as XML. 5. The File Download window appears. The Save As window appears. Navigate to the directory where you want to save the file. select Name at the top of the list to select all the global variables in the list. 4. 2. 2. Optionally. 44 Chapter 6: Exporting Objects from the Repository . 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. 3. To export a global variable: 1. The Export Global Variables page appears. Data Analyzer exports the definitions of all selected global variables. the Export Options button is unavailable. Enter a name for the XML file and click Save.Exporting a Global Variable You can export any global variables defined in the repository. select Name at the top of the list to select all the dashboards in the list. The Export Dashboards page appears. Select the dashboards that you want to export. Click Administration > XML Export/Import > Export Dashboards. Optionally. listing all the global variables in the repository. listing all the dashboards in the repository that you can export. When you export multiple global variables. Click Save. Exporting a Dashboard When you export a dashboard. Click Administration > XML Export/Import > Export Global Variables. You can export more than one dashboard at a time. you cannot select specific components to export. 6.

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

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

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

48 Chapter 6: Exporting Objects from the Repository .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

64 Chapter 7: Importing Objects to the Repository .

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

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

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

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

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

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

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

72 Chapter 8: Using the Import Export Utility .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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.

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 .

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.

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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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.transaction.append property configuring 132 jdbc.log.pollingIntervalSeconds property configuring 132 infa-cache-service.files.log.xml file configuring 135 J Java environment viewing 84 JBoss Application Server description 2 JDBC log file 81.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. 132 jdbc.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.seconds property configuring 132 Index 143 . 132 user security profile 59 using Import Export utility 65 inclusive permissions See access permissions Indicator. 139 showSearchThreshold parameter 90.url property configuring 132 histories clearing 34 clearing schedule 24 holidays creating 29 host. 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.GroupOnAttributePair property configuring 132 groups displaying 90 removing from the repository 10. 11. 12 restricting data access 19 searchLimit parameter 90.timeout.

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 .HeaderFooter. 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.activity. 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.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.abortThresHold property configuring 133 providerContext. 133 logging.xml 139 providerContext.ShrinkToWidth property configuring 133 using 88.properties 128 defining in infa-cache-service.log files JDBC 81 managing 78 logging.maxRowsToDisplay property configuring 79.xml 135 defining in web.estimation.maxInMemory property configuring 133 M mail servers configuring 83 Maps.maxRowsToDisplay property configuring 80.user.

maxSectionsPerPage property configuring 134 report.userReportDisplayMode property configuring 134 ReportingService.compress.jscriptContentEncoding property configuring 135 servlet.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 .syncOnSystemStart property configuring 134 servlet.maxSectionSelectorValues property configuring 134 report.compress property configuring 134 servlet.showSummary property configuring 134 report.removing See deleting report processing time limit defined 85 report.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.maxRowsPerTable property configuring 134 report. 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.frequency property configuring 134 securityadapter.

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. 133 saving 78 viewing and clearing 78 users displaying 90 restricting data access 19 searchLimit parameter 90. 139 showSearchThreshold parameter 90.useDateConversionOnPrimaryDate property configuring 135 timeout changing default for transactions 62 configuring for Data Analyzer session 4 transaction timeout changing the default 62 W web.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. 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. 139 UTF-8 character encoding Data Analyzer support 7 146 Index .

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

Sign up to vote on this title
UsefulNot useful